<xsl:template name="user.header.navigation">
- <xsl:text>
+ <xsl:text>
</xsl:text>
</xsl:template>
<xsl:call-template name="body.attributes"/>
{block name=body}{literal}
<xsl:call-template name="user.header.navigation"/>
-
+
<xsl:call-template name="header.navigation">
<xsl:with-param name="prev" select="$prev"/>
<xsl:with-param name="next" select="$next"/>
<xsl:with-param name="nav.context" select="$nav.context"/>
</xsl:call-template>
-
+
<xsl:call-template name="user.header.content"/>
-
+
<xsl:copy-of select="$content"/>
-
+
<xsl:call-template name="user.footer.content"/>
-
+
<xsl:call-template name="footer.navigation">
<xsl:with-param name="prev" select="$prev"/>
<xsl:with-param name="next" select="$next"/>
<xsl:with-param name="nav.context" select="$nav.context"/>
</xsl:call-template>
-
+
<xsl:call-template name="user.footer.navigation"/>
{/literal}{/block}
<xsl:value-of select="$chunk.append"/>
</xsl:template>
-
+
</xsl:stylesheet>
-<para>
-This filter keeps or removes waypoints based on their proximity to an arc,
-which is a series of connected line segments similar to a route or a track
+<para>
+This filter keeps or removes waypoints based on their proximity to an arc,
+which is a series of connected line segments similar to a route or a track
but without any associated data other than the coordinates. Optionally, it
can move each non-deleted waypoint over the closest segment of the arc.
</para>
-<para>
-The arc may defined in a file whose name must be provided with the
-<option>file</option>, or the tracks or routes that have already been read. That file contains pairs of coordinates for the
+<para>
+The arc may defined in a file whose name must be provided with the
+<option>file</option>, or the tracks or routes that have already been read. That file contains pairs of coordinates for the
vertices of the arc, one coordinate pair per line. Comments may be
-included by preceding them with a '#' character. An arc file looks
+included by preceding them with a '#' character. An arc file looks
something like this sample:
</para>
-<screen format="linespecific">
-# Lima Road/SR3 north of Fort Wayne, Indiana
-41.150064468 -85.166207433
-41.150064468 -85.165371895
-41.149034500 -85.165157318
-41.147832870 -85.164771080
-41.146631241 -85.164384842
-41.144270897 -85.163655281
+<screen format="linespecific">
+# Lima Road/SR3 north of Fort Wayne, Indiana
+41.150064468 -85.166207433
+41.150064468 -85.165371895
+41.149034500 -85.165157318
+41.147832870 -85.164771080
+41.146631241 -85.164384842
+41.144270897 -85.163655281
41.141953468 -85.162882805
</screen>
-<para>
-An arc file may optionally contain gaps in the arc. You may specify
-such a gap by inserting a line containing "#break" either on a line by
+<para>
+An arc file may optionally contain gaps in the arc. You may specify
+such a gap by inserting a line containing "#break" either on a line by
itself or after the coordinates of the starting point of the new arc segment.
</para>
-<example id="example_arc_filter">
+<example id="example_arc_filter">
<title>Using the arc filter</title>
<para>
-Assuming the arc above is in a file called
+Assuming the arc above is in a file called
<filename moreinfo="none">lima_rd.txt</filename>, the following command line
-would include only points within one mile of the section of Lima Road
+would include only points within one mile of the section of Lima Road
covered by the arc.
</para>
<para><userinput>gpsbabel -i geo -f 1.loc -x arc,file=lima_rd.txt,distance=1 -o mapsend -F 2.wpt</userinput></para>
</example>
-
+
<para>When creating a route, points are usually created inside curves or
intersections. That means that, while navigating that route using a
GPS unit, the course pointer would aim to the inside of that curve or
-intersection, and only when you have passed that point will the GPS
+intersection, and only when you have passed that point will the GPS
aim to the next waypoint in the route. This behaviour is useful in
marine navigation but when biking, for instance, it may be a bit late
to decide where to turn to in an intersection.</para>
<para>
This filter is used to "fix" unreliable GPS data by discarding points
-that are believed to be unreliable. You may specify an
+that are believed to be unreliable. You may specify an
HDOP and/or VDOP above a specified limit, a minimum number of satellites
that must have been in view for a fix to be considered, or both.
</para>
</example>
</para>
<para>
-You may specify a minimum number of satellites.
+You may specify a minimum number of satellites.
</para>
<para>
<example id="example_discard_filter_sats">
</example>
</para>
<para> Contributed by Tobias Minich and Serge Droz. </para>
-
+
-<para>
-The duplicate filter is designed to remove duplicate points based on their
-short name (traditionally a waypoint's name on the GPS receiver), and/or
-their location (to a precision of 6 decimals). This filter supports two
-options that specify how duplicates will be recognized,
-<option>shortname</option> and <option>location</option>.
-Generally, at least one of these options is required.
+<para>
+The duplicate filter is designed to remove duplicate points based on their
+short name (traditionally a waypoint's name on the GPS receiver), and/or
+their location (to a precision of 6 decimals). This filter supports two
+options that specify how duplicates will be recognized,
+<option>shortname</option> and <option>location</option>.
+Generally, at least one of these options is required.
</para>
<example id="duplicate_to_suppress_points">
- <title>Using the duplicate filter to suppress points with the same
+ <title>Using the duplicate filter to suppress points with the same
name and location</title>
<para>
This command line removes points that have duplicate short names
- and duplicate locations. The result would be a
- <link linkend="fmt_gpx">gpx</link> file that more than likely
+ and duplicate locations. The result would be a
+ <link linkend="fmt_gpx">gpx</link> file that more than likely
contains only unique points and point data.
</para>
<para><userinput> gpsbabel -i gpx -f 1.gpx -f 2.gpx -x duplicate,location,shortname -o gpx -F merged_with_no_dupes.gpx</userinput></para>
</example>
-
+
-<para>
+<para>
The height filter allows the correction of altitude values.
-At least one popular gps logger does store the ellipsoidal height (sum of the height above mean see level and the height of the geoid above the WGS84 ellipsoid) instead of the height above sea level, as it can be found on maps.
+At least one popular gps logger does store the ellipsoidal height (sum of the height above mean see level and the height of the geoid above the WGS84 ellipsoid) instead of the height above sea level, as it can be found on maps.
-The height filter allows for the correction of these altitude values. This filter supports two options:
+The height filter allows for the correction of these altitude values. This filter supports two options:
-<option>wgs84tomsl</option> and <option>add</option>.
-At least one of these options is required, both can be combined.
+<option>wgs84tomsl</option> and <option>add</option>.
+At least one of these options is required, both can be combined.
</para>
<example id="height_wgs84tomsl">
<title> This option subtracts the WGS84 geoid height from every altitude. For GPS receivers like the iBlue747 the result is the height above mean see level.</title>
<para>You can specify negative numbers to subtract the value. If no unit is specified meters are assumed. For feet you can attach an "f" to the value.</para>
</example>
-
+
<para>
This filter modifies any tracks so that either the distance or the time
between consecutive points is no more than the specified interval. Where
-points are missing, the filter fills them in by following a straight
+points are missing, the filter fills them in by following a straight
line (actually a great circle) between the adjacent points. You
-must specify either the
+must specify either the
<option>distance</option> or the <option>time</option> option.
</para>
<example id="example_interpolate_filter">
</para>
<para><userinput>gpsbabel -i gpx -f track.gpx -x interpolate,distance=2m -o gpx -F newtrack.gpx</userinput></para>
-</example>
+</example>
<para>
If you have a GPX file that contains routes, tracks, and
waypoints and you want a GPX file that contains only tracks,
-you may use this filter to remove the waypoints and the routes
+you may use this filter to remove the waypoints and the routes
with this command:
</para>
<para><userinput>gpsbabel -i gpx -f bigfile.gpx -x nuketypes,waypoints,routes -o gpx -F tracksonly.gpx</userinput></para>
</example>
-
+
<para>
-This option is not required, but if it is not specified the distance
+This option is not required, but if it is not specified the distance
defaults to zero miles, which isn't very useful.
</para>
<para>
-This option specifies the maximum distance a point may be from the arc
+This option specifies the maximum distance a point may be from the arc
without being discarded. Points that are closer to the arc are kept, while
points that are further away are discarded.
</para>
<para>
-When this option is specified, the usual sense of the arc filter is reversed.
+When this option is specified, the usual sense of the arc filter is reversed.
That is, points that are closer than <varname>distance</varname> are discarded
while points that are further away are kept.
</para>
</para>
<para>
GPSBabel supports converting any route or track to a file usable by this
-filter; simply read it in the normal way and write it using the
+filter; simply read it in the normal way and write it using the
<link linkend="fmt_arc">arc</link> file format.
</para>
<para>
-When this option is specified, only points that are within the specified
+When this option is specified, only points that are within the specified
distance of one of the vertices of the arc are kept. This differs from the
normal mode of operation in that in the normal mode, points that are close to
the lines between points are also kept.
<para>
-This option drops waypoints with an altitude lower than the specified
-value (in meters). Although GPS altitude isn't very accurate,
-GPS devices may log faulty waypoints from time to time, such as when
+This option drops waypoints with an altitude lower than the specified
+value (in meters). Although GPS altitude isn't very accurate,
+GPS devices may log faulty waypoints from time to time, such as when
near tall buildings. Elevation values that are way off may signify such waypoints. Use this option to the filter to toss known rogue points.
</para>
<para>
-This option specifies the maximum allowable Horizontal Dilution of
-Precision (HDOP). By default, any point with an HDOP in excess of
-this value will be discarded regardless of its VDOP, but see
+This option specifies the maximum allowable Horizontal Dilution of
+Precision (HDOP). By default, any point with an HDOP in excess of
+this value will be discarded regardless of its VDOP, but see
<option>hdopandvdop</option>.
</para>
<para>
-If this option is used, only points that exceed both the maximum
+If this option is used, only points that exceed both the maximum
allowable HDOP and the maximum allowable VDOP will be discarded. This
-option requires that both the <option>hdop</option> and
-<option>vdop</option> options be specified.
+option requires that both the <option>hdop</option> and
+<option>vdop</option> options be specified.
</para>
<para>
-This option discards points that have shortnames that match the
+This option discards points that have shortnames that match the
provided regular expression.
</para>
<example id="discarding_points_with_names">
<para>
-This option specifies the maximum allowable Vertical Dilution of
-Precision (VDOP). By default, any point with an VDOP in excess of
-this value will be discarded regardless of its HDOP, but see
+This option specifies the maximum allowable Vertical Dilution of
+Precision (VDOP). By default, any point with an VDOP in excess of
+this value will be discarded regardless of its HDOP, but see
<option>hdopandvdop</option>.
</para>
When this option is specified, GPSBabel will remove all instances of a
duplicated waypoint, not just the second and subsequent instances. If
your input file contains waypoints A, B, B, and C, the output file will
-contain waypoints A, B, and C without the <option>all</option> option,
+contain waypoints A, B, and C without the <option>all</option> option,
or just A and C with the <option>all</option> option.
</para>
<example id="duplicate_to_ignore">
<title>Using the duplicate filter to implement an "ignore list."</title>
<para>
-This option may be used to implement an "ignore list." In the following
+This option may be used to implement an "ignore list." In the following
example, the duplicate filter is used to remove a list of waypoints to be
ignored from a larger collection of waypoints:
</para>
<para>
-This option is used to change the locations of waypoints without losing any
-of the other associated information. When this option is specified, the
+This option is used to change the locations of waypoints without losing any
+of the other associated information. When this option is specified, the
latitude and longitude from later duplicates will replace the latitude and
longitude in the original waypoint.
</para>
<para>
-As an example, this option may be used to adjust the locations of "puzzle"
+As an example, this option may be used to adjust the locations of "puzzle"
geocaches in a Groundspeak pocket query:
</para>
<example id="Correcting_Cache_Locations">
geocaches</title>
<para><userinput>gpsbabel -i gpx -f 43622.gpx -i csv -f corrections.csv -x duplicate,shortname,correct -o gpx -F 43622-corrected.gpx</userinput></para>
<para>
-After this command is run, the waypoints in the output file will have all
-of the descriptive information from <filename>43622.gpx</filename>, but
-waypoints that were also found in <filename>corrections.csv</filename>
+After this command is run, the waypoints in the output file will have all
+of the descriptive information from <filename>43622.gpx</filename>, but
+waypoints that were also found in <filename>corrections.csv</filename>
will have their coordinates replaced with the coordinates from that file.
</para>
</example>
<para>
-This option causes the duplicate filter to remove any additional waypoint
-that has the same coordinates (to six decimal degrees) as a waypoint that
-came before. This option may be used to remove duplicate waypoints if the
+This option causes the duplicate filter to remove any additional waypoint
+that has the same coordinates (to six decimal degrees) as a waypoint that
+came before. This option may be used to remove duplicate waypoints if the
names are not expected to be the same. It also might be used along with the
-<option>shortname</option> option to remove duplicate waypoints if the names
+<option>shortname</option> option to remove duplicate waypoints if the names
of several unrelated groups of waypoints might be the same.
</para>
<para>
-This option is the one most often used with the duplicate filter. This
+This option is the one most often used with the duplicate filter. This
option instructs the duplicate filter to remove any waypoints that share
a short name with a waypoint that has come before. This option might be
-used to remove duplicates if you are merging two datasets that were
+used to remove duplicates if you are merging two datasets that were
each created in part from a common ancestor dataset.
</para>
<para>
-If this option is specified, the interpolate filter interpolates routes
+If this option is specified, the interpolate filter interpolates routes
rather than tracks. Because route points do not have time stamps, it is an
error to use this option with the <option>time</option> option.
</para>
<para>
-This option causes the nuketypes filter to discard all waypoints that are not
+This option causes the nuketypes filter to discard all waypoints that are not
associated with a track or route.
</para>
<para>
-When this option is specified, the usual sense of the polygon filter is
+When this option is specified, the usual sense of the polygon filter is
reversed. That is, points that are inside the polygon are discarded
while points that are further away are kept.
</para>
</para>
<para>
GPSBabel supports converting any route or track to a file usable by this
-filter; simply read it in the normal way and write it using the
-<link linkend="fmt_arc">arc</link> file format. Afterward, you will
-need to make sure that the first point and the last point in the
+filter; simply read it in the normal way and write it using the
+<link linkend="fmt_arc">arc</link> file format. Afterward, you will
+need to make sure that the first point and the last point in the
file are the same, as the polygon filter depends on that. You can do so
with any text editor.
</para>
<para>
-This option specifies the minimum allowable distance between two points. If
+This option specifies the minimum allowable distance between two points. If
two points are closer than this distance, only one of them is kept.
</para>
<para>
-Distances may be expressed in feet (30f) or meters (10m). If no unit is
+Distances may be expressed in feet (30f) or meters (10m). If no unit is
specified, the distance is assumed to be in feet.
</para>
<para>
- Specifies the maximum time in seconds between any two points. If the
- time difference is larger than what's specified here, the points will
+ Specifies the maximum time in seconds between any two points. If the
+ time difference is larger than what's specified here, the points will
not be discarded.
</para>
<para>
<option>nosort</option> option is also specified.)
</para>
<para>
-Note that this route is not necessarily the most efficient route to visit
-all of the points. In fact, for some data sets, it might be the least
+Note that this route is not necessarily the most efficient route to visit
+all of the points. In fact, for some data sets, it might be the least
efficient route.
</para>
<para>
This option specifies the maximum distance a point may be from the central
point in order to remain in the dataset. Points closer than this distance
-will be kept and points further away will be removed (unless the
+will be kept and points further away will be removed (unless the
<option>exclude</option> option is specified.)
</para>
<para>
<para>
This option specifies the maximum number of points that the radius filter may
-keep. If there are more than this number of points within the specified
+keep. If there are more than this number of points within the specified
distance of the center, the more distant points will be discarded even though
-they are within the specified distance. If this option is not specified,
+they are within the specified distance. If this option is not specified,
all points are kept regardless of how many there are.
</para>
<para>
-Note that if the <option>nosort</option> option is also specified, this
+Note that if the <option>nosort</option> option is also specified, this
option will instead keep points based on their position within the input
file rather than on their distance from the center. This may or may not be
what you want.
</para>
<para>
-Note, too, that this option may be used with the <option>exclude</option>
-option, but the results might not be what you expect. In particular, the
-results will not be the same as if you had kept all of the points you'd
-otherwise throw away. You will still get no more than
-<varname>maxcount</varname> points, but they will all be at least
+Note, too, that this option may be used with the <option>exclude</option>
+option, but the results might not be what you expect. In particular, the
+results will not be the same as if you had kept all of the points you'd
+otherwise throw away. You will still get no more than
+<varname>maxcount</varname> points, but they will all be at least
<varname>distance</varname> away from the center. (And possibly sorted.)
</para>
-
+
<para>
This option specifies the maximum number of points which may appear in the
simplified route. For example, if you specify "count=50", all resulting
-routes will contain 50 points or fewer.
+routes will contain 50 points or fewer.
</para>
<para>
You must specify either this option or the <option>error</option> option.
<para>
-This option instructs GPSBabel to remove points that have the smallest
+This option instructs GPSBabel to remove points that have the smallest
overall effect on the overall shape of the route. Using this method, the
-first point to be removed will be the one that is closest to a line drawn
+first point to be removed will be the one that is closest to a line drawn
between the two points adjacent to it.
</para>
<para>
This option specifies the maximum allowable error that may be introduced
by removing a single point. Used with the <option>length</option>
and <option>crosstrack</option> methods, the value of this option is a distance,
-specified in miles by default. You may also specify the distance in
+specified in miles by default. You may also specify the distance in
kilometers by adding a 'k' to the end of the number.
For the <option>relative</option> method it is a dimensionless quantity.
</para>
-<para>
+<para>
How the error is determined depends on whether the <option>length</option>,
<option>crosstrack</option>, or <option>relative</option> method is used.
If you are using the length method, the error is the change in the length of
<para>
This option instructs GPSBabel to simplify by removing points that cause the
-smallest change in the overall length of the route first.
+smallest change in the overall length of the route first.
</para>
<para>
-This option is only valid in conjunction with the <option>pop</option>.
+This option is only valid in conjunction with the <option>pop</option>.
When it is specified, the topmost collection of data from the stack is
appended to the current collection of data.
</para>
<para>
This option is only valid when used with the <option>push</option> option.
-When this option is specified, a copy of the current state is pushed onto
-the stack but the current state is left unchanged. Otherwise, the push
+When this option is specified, a copy of the current state is pushed onto
+the stack but the current state is left unchanged. Otherwise, the push
operation clears the current data collection.
</para>
This is one of three "primary" options to the stack filter.
</para>
<para>
-This option "pops" the collection of data from the top of the stack.
-By default, the saved state replaces the current state, but see the
-<option>discard</option> and <option>append</option> options for
+This option "pops" the collection of data from the top of the stack.
+By default, the saved state replaces the current state, but see the
+<option>discard</option> and <option>append</option> options for
alternatives.
</para>
</para>
<para>
When this option is specified, the current state is pushed onto the top of
-the stack. By default, the current state is then cleared, but the
+the stack. By default, the current state is then cleared, but the
<option>copy</option> option can be used to cause it to be saved.
</para>
<para>
This option is only valid when used with the <option>pop</option> option.
-This is the default behavior of the <option>pop</option> option, so you
-should never need to specify it, but it is included for the sake of
-readability. When this option is specified, the popped state replaces
+This is the default behavior of the <option>pop</option> option, so you
+should never need to specify it, but it is included for the sake of
+readability. When this option is specified, the popped state replaces
the current state.
</para>
<para>
-This option computes (or recomputes) a value for the GPS heading at each
-trackpoint. This is most useful with trackpoints from formats that don't
-support heading information or for trackpoints synthesized by the
+This option computes (or recomputes) a value for the GPS heading at each
+trackpoint. This is most useful with trackpoints from formats that don't
+support heading information or for trackpoints synthesized by the
<link linkend="filter_interpolate">interpolate</link>
filter. The heading at each trackpoint is simply the course from the
previous trackpoint in the track. The first trackpoint in each track
-<para>
+<para>
This option is used in conjunction with the merge option to discard track points with missing
timestamps instead of aborting with the "Found track point at lat,lon without time!" error.
</para>
<example id="ex_track_discard">
<title>Merging tracks with missing timestamps with the track filter</title>
-<para>
+<para>
Suppose you want to merge tracks that may have missing timestamps. To do that, use this command line:
</para>
<para><userinput>gpsbabel -t -i gpx -f john.gpx -f doe.gpx -x track,merge,discard -o gpx -F john_doe.gpx</userinput></para>
value. Valid values for this option are PPS, DGPS, 3D, 2D, or NONE.
</para>
<para>
-This option is most useful when converting from a format that doesn't
+This option is most useful when converting from a format that doesn't
contain GPS fix status to one that requires it.
</para>
-<para>
-This option puts all track points from all tracks into a single track
+<para>
+This option puts all track points from all tracks into a single track
and sorts them by time stamp. Redundant points with identical time stamps will be dropped.
</para>
<example id="ex_track_merge">
<title>Merging tracks with the track filter</title>
-<para>
-Suppose you want to merge tracks recorded with two different GPS devices
+<para>
+Suppose you want to merge tracks recorded with two different GPS devices
at the same time. To do that, use this command line:
</para>
<para><userinput>gpsbabel -t -i gpx -f john.gpx -i gpx -f doe.gpx -x track,merge,title="COMBINED LOG" -o gpx -F john_doe.gpx</userinput></para>
</para>
<para>
This step is performed last by this filter and is used to clean up earlier
-simplifications that may have left tracks with so few points as to be
+simplifications that may have left tracks with so few points as to be
useless, such as a track taken while stationary but with GPS wander.
</para>
-<para>
+<para>
This option causes all tracks to be appended to one another to form a single
track. This option does not work if any two tracks overlap in time; in that
-case, consider using the <option>merge</option> option.
+case, consider using the <option>merge</option> option.
</para>
<para>
This option is most useful for rejoining tracks that might have
is greater than the distance given as a parameter.
The distance must be numeric and can be in miles or kilometers,
expressed as one of the character "k", or "m".
- If sdistance is given no parameters, this option has the same
- effect as the split option without parameters. If there is more
+ If sdistance is given no parameters, this option has the same
+ effect as the split option without parameters. If there is more
than one track,
use the pack option before before using this.</para>
<para> For example, to split the track if the distance between
points is greater than 100 meters, use this:</para>
<para><userinput>
-gpsbabel -t
- -i gpx -f in.gpx
- -x track,pack,sdistance=0.1k"
+gpsbabel -t
+ -i gpx -f in.gpx
+ -x track,pack,sdistance=0.1k"
-o gpx -F out.gpx
</userinput></para>
<para> The sdistance option can be combined with the split option.
The track then will be split only if both time and distance
- interval exceeds the supplied values. This technique can be used to
+ interval exceeds the supplied values. This technique can be used to
filter out gaps from
the tracklog. The gap is kept only if the gps device is without
- signal for longer time than that given and during that time it moves
+ signal for longer time than that given and during that time it moves
a distance over that given.
This example splits the track
if the device is without signal for at least 5 minutes
and during this time moves more than 300 meters:</para>
<para><userinput>
-gpsbabel -t
- -i gpx -f in.gpx
- -x track,pack,sdistance=0.3k,split=5m
+gpsbabel -t
+ -i gpx -f in.gpx
+ -x track,pack,sdistance=0.3k,split=5m
-o gpx -F out.gpx
</userinput></para>
<para>
This option computes a value for the GPS speed at each trackpoint.
This is most useful with trackpoints from formats that don't support
-speed information or for trackpoints synthesized by the
+speed information or for trackpoints synthesized by the
<link linkend="filter_interpolate">interpolate</link>
filter.</para>
<para>
The speed at each trackpoint is the average speed from the
-previous trackpoint (distance divided by time). The first trackpoint
+previous trackpoint (distance divided by time). The first trackpoint
in each track is assigned a speed of "unknown."
</para>
<para>
<para><userinput> gpsbabel -t -i gpx -f in.gpx -x track,split,title="ACTIVE LOG # %Y%m%d" -o gpx -F out.gpx</userinput></para>
<para> If the input has multiple tracks, pack them together before
splitting them back apart per day thusly: </para>
- <para><userinput> gpsbabel -t -i gpx -f in.gpx
- -x track,pack,split,title="ACTIVE LOG # %D"
+ <para><userinput> gpsbabel -t -i gpx -f in.gpx
+ -x track,pack,split,title="ACTIVE LOG # %D"
-o gpx -F out.gpx</userinput></para>
<para> Additionally you can add an interval to the split
option. With this the track will be split if the time
</para>
<para> For example, to split a track based on an four hour
interval, use this:</para>
- <para><userinput>
-gpsbabel -t
- -i gpx -f in.gpx
- -x track,pack,split=4h,title="LOG # %c"
+ <para><userinput>
+gpsbabel -t
+ -i gpx -f in.gpx
+ -x track,pack,split=4h,title="LOG # %c"
-o gpx -F out.gpx
</userinput></para>
<para>
-This option is used along with the <option>stop</option> to discard
-trackpoints that were recorded outside of a specific period of time.
+This option is used along with the <option>stop</option> to discard
+trackpoints that were recorded outside of a specific period of time.
This option specifies the beginning of the time period.
</para>
<para>
If this option is not specified, the time period is assumed to begin at the
-dawn of time or January 1, 1970, whichever was later. The time for this
-option is expressed in UTC.
+dawn of time or January 1, 1970, whichever was later. The time for this
+option is expressed in UTC.
</para>
<para>
The value of this option must be in the form of YYYYMMDDHHMMSS, but it is
-not necessary to specify the smaller time units if they are not needed.
+not necessary to specify the smaller time units if they are not needed.
That is, if you only care about points logged between 10 AM and 6 PM on a
given date, you need not specify the minutes or seconds.
</para>
<para>
To get only the parts of a track that were mapped on 20 July 2005
between 10 AM and 6 PM, use this command line:
-</para>
+</para>
<para><userinput>gpsbabel -t -i gpx -f in.gpx -x track,start=2005072010,stop=2005072018 -o gpx -F out.gpx </userinput></para>
</example>
<para>
-This option is used in conjunction with the <option>start</option> option to
-discard all trackpoints outside of a given period of time. This option
+This option is used in conjunction with the <option>start</option> option to
+discard all trackpoints outside of a given period of time. This option
defines the end of the time period.
</para>
<para>
-If this option is not specified, the time period is assumed to end at the
+If this option is not specified, the time period is assumed to end at the
end of civilization as we know it or the year 2038, whichever comes first.
The time for this option is expressed in UTC.
</para>
<para>
-See the <option>start</option> option for the format of this value and an
+See the <option>start</option> option for the format of this value and an
example of usage.
</para>
-<para>
+<para>
This option specifies a title for tracks generated by the track filter.
-By default, the title of the new track is composed of the start time of
+By default, the title of the new track is composed of the start time of
the track appended to this value.
</para>
<para>
-If this value contains a percent (%) character, it is treated as a format
-string for the POSIX strftime function, allowing custom time-based
-track names.
+If this value contains a percent (%) character, it is treated as a format
+string for the POSIX strftime function, allowing custom time-based
+track names.
</para>
<para>
This option, when used in connection with the wpt, rte, or trk options, tells
-GPSBabel to delete the source data after conversion. This is most useful if
+GPSBabel to delete the source data after conversion. This is most useful if
you are trying to avoid duplicated data in the output.
</para>
<example id="transform_del">
-<para>\r
-With this option you can decide to let GPSBabel name generated route points according to their source track name.\r
-</para>\r
-<para>\r
-GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>\r
-<para>\r
-Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes.\r
-</para>\r
-<example id="transform_rptname">\r
-<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>\r
-<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx</userinput></para>\r
-</example>\r
+<para>
+With this option you can decide to let GPSBabel name generated route points according to their source track name.
+</para>
+<para>
+GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>
+<para>
+Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially usefull if several differently named tracks are contained in the source file which should each be transformed into routes.
+</para>
+<example id="transform_rptname">
+<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>
+<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx</userinput></para>
+</example>
<example id="transform_to_rte">
<title>Converting a pile of waypoints to a GPX route</title>
<para>
-Say you you have a data file that came from CSV file that you want to convert
+Say you you have a data file that came from CSV file that you want to convert
to a GPX route that can be loaded into Basecamp. Use the following command:
</para>
<para><userinput>gpsbabel -i csv -f blah.txt -x transform,rte=wpt -o gdb -F blah.gdb</userinput></para>
<para>
-This option selects the destination type of this filter to be tracks.
-Choose this when you want to create tracks from a list of waypoints or routes.
+This option selects the destination type of this filter to be tracks.
+Choose this when you want to create tracks from a list of waypoints or routes.
A single track will be created in the sequence they appear in the input.
</para>
<example id="transform_to_trk">
<title>Converting a pile of waypoints to a GPX track</title>
<para>
-Say you you have a data file that came from CSV file that you want to convert
+Say you you have a data file that came from CSV file that you want to convert
to a GPX track that can be loaded into Basecamp. Use the following command:
</para>
<para><userinput>gpsbabel -i csv -f blah.txt -x transform,trk=wpt -o gdb -F blah.gdb</userinput></para>
<para>
-This option selects the destination type of this filter to be waypoints.
+This option selects the destination type of this filter to be waypoints.
Choose this when you want to convert tracks or routes into waypoints.
</para>
<example id="transform_to_wpt">
<para>
-This option will output verbose messages reporting the state of the internal data structures holding waypoints, routes and tracks. Detected problems will normally produce a fatal error, but with this option in effect no error will be thrown allowing continued processing.
+This option will output verbose messages reporting the state of the internal data structures holding waypoints, routes and tracks. Detected problems will normally produce a fatal error, but with this option in effect no error will be thrown allowing continued processing.
</para>
-<para>
+<para>
The polygon filter includes points if they are inside
-of a polygon. A polygon file looks like an
+of a polygon. A polygon file looks like an
<link linkend="filter_arc">arc</link> file, except
that the arc it describes must be a closed cycle. That is,
for a simple polygon, the first and last points must be the
42.0000 -85.0000
41.0000 -85.0000
</screen>
-<para>
+<para>
Polygons may include islands and holes. To include an
island or a hole, just append it to the main polygon.
</para>
<para>
As with the arc filter, you define a polygon by
giving the name of the file that contains it, using
-the <option>file</option> option.
+the <option>file</option> option.
</para>
-<para>
+<para>
Note that this filter currently will not work properly
if your polygon contains one or both poles or if it spans the
line of 180 degrees east or west longitude.
</para>
<example id="example_polygon_filter">
<title>Using the polygon filter</title>
-<para>
-Suppose you have a polygon file that defines the border of your county,
-called mycounty.txt. This command line will give you only the points
+<para>
+Suppose you have a polygon file that defines the border of your county,
+called mycounty.txt. This command line will give you only the points
in your county:
</para>
<para><userinput>gpsbabel -i geo -f 1.loc -x polygon,file=mycounty.txt -o mapsend -F 2.wpt</userinput></para>
</example>
<example id="example_in_or_close_to">
-<title>Using the polygon and arc filters to find points in or nearly in a
+<title>Using the polygon and arc filters to find points in or nearly in a
polygon</title>
<para>
Because the polygon and <link linkend="filter_arc">arc</link> filters use
the same file format, you can use them together to find all points that are
-"in or nearly in" a polygon. This can be useful if your waypoints or the
-boundaries of your polygon are not quite perfect, so you want to provide a
-buffer zone around it in case there are points nearby that should be in the
+"in or nearly in" a polygon. This can be useful if your waypoints or the
+boundaries of your polygon are not quite perfect, so you want to provide a
+buffer zone around it in case there are points nearby that should be in the
polygon but aren't quite.
</para>
<para><userinput>
-gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt
--x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append
+gpsbabel -i gpx -f points.gpx -x stack,push -x polygon,file=mycounty.txt
+-x stack,swap -x arc,file=mycounty.txt,distance=1k -x stack,pop,append
-x duplicate,shortname -o gpx -F nearmycounty.gpx
</userinput></para>
<para>
This command makes a copy of the points, finds the ones that are in your
your county, swaps that result with the copy of the original set of points,
-finds the ones from that set that are within 1 km of the border of the county,
+finds the ones from that set that are within 1 km of the border of the county,
puts the two lists together, and then filters out any points that appear twice
-(This step is necessary because points inside the county but near the county
+(This step is necessary because points inside the county but near the county
line will be kept by both the polygon and the arc filter.)
</para>
</example>
-<para>
+<para>
This filter removes points based on their proximity to each other.
For waypoints a point is removed if it is within the specified distance of a preceeding point.
For routes and tracks consecutive points are removed until the distance between the bracketing points is greater than the specified distance.
<example id="posn_to_suppress_close_points">
<title>Using the position filter to suppress close points</title>
<para>
-The following command removes multiple points that are within
+The following command removes multiple points that are within
one foot of each other, leaving just one.
</para>
<para><userinput>gpsbabel -i geo -f 1.loc -f 2.loc -x position,distance=1f -o mapsend -F 3.wpt</userinput></para>
</example>
-
+
-<para>
-This filter includes or excludes waypoints based on their proximity to a
-central point. All waypoints more than the specified distance from the
+<para>
+This filter includes or excludes waypoints based on their proximity to a
+central point. All waypoints more than the specified distance from the
specified point will be removed from the dataset.
</para>
<para>
-By default, all remaining points are sorted so that points closer to the
+By default, all remaining points are sorted so that points closer to the
center appear earlier in the output file.
</para>
<example id="radius_to_find_points_close">
<para><userinput>gpsbabel -i geo -f 1.loc -x radius,distance=1.5M,lat=30.0,lon=-90.0 -o mapsend -F 2.wpt</userinput></para>
</example>
-
+
-
+
<para> The reverse filter is used to reverse tracks and routes.
It's mostly useful for those few formats where track/route
sequence matters and there isn't a way to reverse them using
will be in for unpleasant ride. application cares about
timestamps
</para>
-
+
-<para>
-The Simplify filter is used to simplify routes and tracks for use with
-formats that limit the number of points they can contain or just to
+<para>
+The Simplify filter is used to simplify routes and tracks for use with
+formats that limit the number of points they can contain or just to
reduce the complexity of a route.
</para>
<para>
-The filter attempts to remove points from each route until the number
-of points or the error is within the given bounds, while also attempting
-to preserve the shape of the original route as much as possible.
+The filter attempts to remove points from each route until the number
+of points or the error is within the given bounds, while also attempting
+to preserve the shape of the original route as much as possible.
</para>
-<para>
-The quality of the results will vary depending on the density of points
+<para>
+The quality of the results will vary depending on the density of points
in the original route and the length of the original route.
</para>
-<para>
-For example, suppose you have a route from Street Atlas 2003 that you
-wish to use with a Magellan GPS receiver that only supports up to 50 points
+<para>
+For example, suppose you have a route from Street Atlas 2003 that you
+wish to use with a Magellan GPS receiver that only supports up to 50 points
in a route:
</para>
<para><userinput>gpsbabel -r -i saroute -f RoadTrip.anr -x simplify,count=50 -o magellan -F grocery.rte</userinput></para>
-
+
<para>
This filter sorts waypoints, routes and/or tracks by the selected field(s).
</para>
-
+
-<para>
-This filter is designed to solve advanced problems that involve shuffling
-multiple lists of waypoints, tracks, or routes.
+<para>
+This filter is designed to solve advanced problems that involve shuffling
+multiple lists of waypoints, tracks, or routes.
</para>
<para>
The stack filter can be used to save the current state of the entire
so you can simultaneously have as many stored collections of data as you
can fit in your computer's memory.
</para>
-<para>
+<para>
The stack filter can be used in conjunction with other
filters to implement a "union" or "logical or" functionality.
The basic idea is to use the stack to store copies of the
duplicates can be removed with the DUPLICATE filter; see
above.)
</para>
- <para><userinput>
-gpsbabel -i gpx -f in.gpx
- -x stack,push,copy
- -x polygon,file=county_a.txt
- -x stack,swap
- -x polygon,file=county_b.txt
- -x stack,pop,append
+ <para><userinput>
+gpsbabel -i gpx -f in.gpx
+ -x stack,push,copy
+ -x polygon,file=county_a.txt
+ -x stack,swap
+ -x polygon,file=county_b.txt
+ -x stack,pop,append
-o gpx -F out.gpx
</userinput></para>
<para> This example reads a large list of waypoints and
writing the waypoint descriptions into two different PalmDoc
files and exporting all of the points to the GPS receiver:
</para>
- <para><userinput>
-gpsbabel -i gpx -f indiana.gpx
- -x stack,push,copy
- -x radius,lat=41.0765,lon=-85.1365,distance=20m
- -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb
- -x stack,swap
- -x radius,lat=39.7733,lon=-86.1433,distance=20m
- -o palmdoc,dbname=Indianapolis -F indianapolis.pdb
- -x stack,pop,append
+ <para><userinput>
+gpsbabel -i gpx -f indiana.gpx
+ -x stack,push,copy
+ -x radius,lat=41.0765,lon=-85.1365,distance=20m
+ -o palmdoc,dbname=Fort\ Wayne -F fortwayne.pdb
+ -x stack,swap
+ -x radius,lat=39.7733,lon=-86.1433,distance=20m
+ -o palmdoc,dbname=Indianapolis -F indianapolis.pdb
+ -x stack,pop,append
-o magellan -F fwaind.wpt
</userinput></para>
-
+
This filter performs various operations on track data.
</para>
-
+
<para>
-This format is used by GPSBabel itself as the input to the
-<link linkend="filter_arc">arc</link> and
+This format is used by GPSBabel itself as the input to the
+<link linkend="filter_arc">arc</link> and
<link linkend="filter_polygon">polygon</link> filters. See those filters
for more information.
</para>
<para>
-The arc format reads two numeric fields, a latitude and a longitude,
-in any format recognized as <link linkend="style_def_lathuman">human
+The arc format reads two numeric fields, a latitude and a longitude,
+in any format recognized as <link linkend="style_def_lathuman">human
readable</link> and writes as simple degrees decimal. It really is
intended for GPSBabel's own internal use more than general use, though
-it turns out to be a convenient way of expressing simple polylines and
+it turns out to be a convenient way of expressing simple polylines and
polygons.
</para>
<para>Serial download protocol for the <ulink url="http://www.brauniger.com">Brauniger</ulink> IQ series of
-barograph recording flight instruments. This format creates a
-track of altitude vs time which can be merged with a GPS track
+barograph recording flight instruments. This format creates a
+track of altitude vs time which can be merged with a GPS track
of the same flight to create a three dimensional IGC file. </para>
-<para>
-This file format (extension .bcr) is used in Map&Guide
-<productname>Motorrad Routenplaner 2002</productname> and later versions.
-BCR is a route-only format. If you own a newer release (2005 or later) you
-may also use the XML export with GPSBabel's <link linkend="fmt_tef">tef</link>
-input format.
+<para>
+This file format (extension .bcr) is used in Map&Guide
+<productname>Motorrad Routenplaner 2002</productname> and later versions.
+BCR is a route-only format. If you own a newer release (2005 or later) you
+may also use the XML export with GPSBabel's <link linkend="fmt_tef">tef</link>
+input format.
</para>
<para>
There may be other products from Map&Guide that use this format as well.
</para>
-<para>
+<para>
Coordinates are stored in a BCR file in a Mercator projection. The
-conversion from the Mercator projection to polar (latitude/longitude)
-coordinates and back again may result in visible differences. Experience
+conversion from the Mercator projection to polar (latitude/longitude)
+coordinates and back again may result in visible differences. Experience
reports are welcome.
</para>
<example id="sample_bcr_command">
<title>Sample BCR command with all options</title>
<para><userinput>gpsbabel -r -i gpx -f in.gpx -o bcr,index=1,name="From A to B",radius=6371012 -F a_to_b.bcr</userinput></para>
</example>
-
+
<para>
-This format supports reading and writing wayponts to
-<ulink url="http://www.bushnell.com/products/gps/">Bushnell GPS</ulink>
+This format supports reading and writing wayponts to
+<ulink url="http://www.bushnell.com/products/gps/">Bushnell GPS</ulink>
receivers, notably the <productname>Onix 400</productname>.
</para>
<para>
-It's an oddity for many GPSBabel norms that this format requires each
-waypoint be in a separate file. Our "output filename" argument, -F is
+It's an oddity for many GPSBabel norms that this format requires each
+waypoint be in a separate file. Our "output filename" argument, -F is
modified to take an "output filename template". The output filename
you specify will have a dash, and a sequentially increasing integer,
and the ".wpt" extension appended to it. When the names are shown on
<para>
At least for the 200CR, the directory name used by the device is "WAYPOINT"
in the root directory. It's also worth mentioning that its USB Mass Storage
-protocol appears to not work on (at least) Snow Leopard 10.6.2. It's not
+protocol appears to not work on (at least) Snow Leopard 10.6.2. It's not
known if other Onix models have a more compatible USB implementation.
</para>
<para>
-This format supports tracks from
-<ulink url="http://www.bushnell.com/products/gps/">Bushnell GPS</ulink>
+This format supports tracks from
+<ulink url="http://www.bushnell.com/products/gps/">Bushnell GPS</ulink>
receivers, notably the <productname>Onix 400</productname>.
</para>
<para>
This format reads individual .trl files as written by the GPS. As this is
-a reverse-engineered format, it's not understood how (or even if) long
-tracks, in
+a reverse-engineered format, it's not understood how (or even if) long
+tracks, in
particular, span multiple files so initially this format is most effective
on tracks under a few thousand points.
</para>
most we believe these units can represent in a track.
</para>
<para>
- The output base filename, converted to uppercase and stripped of
- everything but letters and digits, is used for the trail name inside
+ The output base filename, converted to uppercase and stripped of
+ everything but letters and digits, is used for the trail name inside
the file itself.
</para>
-
-
- <para>Support for
-<ulink url="http://www.cambridge-aero.com/products.htm">Cambridge</ulink>
-and <ulink url="http://www.winpilot.com"> Winpilot</ulink>
+
+
+ <para>Support for
+<ulink url="http://www.cambridge-aero.com/products.htm">Cambridge</ulink>
+and <ulink url="http://www.winpilot.com"> Winpilot</ulink>
flight analysis and planning software for glider pilots. </para>
-
+
-
-
+
+
<para>This is the format used by <productname>CoastalExplorer</productname>. The
format is XML with items uniquely identified by Windows-style UUIDs.
<ulink url="http://www.rosepointnav.com">http://www.rosepointnav.com</ulink>
</para>
-
+
-
+
<para> There are a billion variants of Comma Separated Value
data. This is the one specifically that makes <ulink url="http://www.delorme.com">DeLorme</ulink> <productname>S&A Deluxe 9</productname> happy. It's
also a very simple program and useful for many other programs like
spreadsheets, but contains only a very minimal information. For general
-purpose use, you'll probably be more happy with our
+purpose use, you'll probably be more happy with our
<link linkend="fmt_unicsv">universal csv (unicsv)</link> format.</para>
- <para> CSV is also the correct format for
+ <para> CSV is also the correct format for
<productname>Lowrance MapCreate</productname>,
their commercial mapping program, or GDM6 (their free waypoint
manager) for iFinder which is available at <ulink url="http://www.lowrance.com/Software/GDM6/Default.asp">lowrance.com</ulink>
</para>
<para>
- On write, this format writes simple "latitude, longitude" pairs, but
+ On write, this format writes simple "latitude, longitude" pairs, but
on read it will read anything supported by our <link linkend="style_def_lathuman">human readable</link> definition.
</para>
<para>
<para>
- This format supports flight analysis data from the
- <ulink url="http://www.seeyou.ws/">See You</ulink>
+ This format supports flight analysis data from the
+ <ulink url="http://www.seeyou.ws/">See You</ulink>
program.
</para>
<para>
- Position information is preserved, but the aviation-specific
+ Position information is preserved, but the aviation-specific
information such as runway length and airport frequency, are
written as blanks and ignored on read.
</para>
for debugging purposes when developing a new format module for GPSBabel.
</para>
<para>
-To understand the contents of this file, look at the
+To understand the contents of this file, look at the
<filename>style/custom.style</filename> file in the GPSBabel source
distribution as well as <xref linkend="Styles" />.
</para>
</para>
<para>
The basic information was found at <ulink url="http://mozoft.com/d3log.html">mozoft.com</ulink>.
- In addition to the standard GPS track data of coordinates and timestamp, this format also stores the
- position fix and the number of satellites seen during recording.
+ In addition to the standard GPS track data of coordinates and timestamp, this format also stores the
+ position fix and the number of satellites seen during recording.
</para>
<para>
<productname>Destinator</productname> by
<para>
- Serial download protocol for the <productname>GlobalSat DG-100</productname>,
- <productname> GlobalSat BT-335</productname>,
+ Serial download protocol for the <productname>GlobalSat DG-100</productname>,
+ <productname> GlobalSat BT-335</productname>,
and <productname>GlboalSat BT-338X</productname>GPS data loggers.
</para>
<para>
- While the DG-100 has a button to record waypoints, they seem to be indistinguishable
- from trackpoints. Therefore, all points will be presented as trackpoints,
+ While the DG-100 has a button to record waypoints, they seem to be indistinguishable
+ from trackpoints. Therefore, all points will be presented as trackpoints,
regardless of whether they were recorded automatically or manually.
</para>
<para>
<para>
This format can be used to convert files from
- <ulink url="http://www.tracklogs.co.uk">TrackLogs Digital Mapping</ulink>. The files
+ <ulink url="http://www.tracklogs.co.uk">TrackLogs Digital Mapping</ulink>. The files
have extension .trl and can contain waypoints and tracks.
</para>
<para>
- We have seen three different types of this format. Two are binary
- and one is an XML based format. All three types are supported
+ We have seen three different types of this format. Two are binary
+ and one is an XML based format. All three types are supported
by our reader.
</para>
<para>
command. Reading the binary Markers.jwp format directly off the data
card is not supported yet. Contributed by Tim Zickus.
</para>
-
+
Information about and sketchy code to implement this file
format were provided by Eric Cloninger.
</para>
-
+
<para>
The <ulink url="http://www.energympro.com/product/dsw-gps-sport-watch/">
Energympro GPS sport watches</ulink> present themselves as USB mass storage
- devices. To get the training just connect the device using the supplied
-USB cable to your computer and the device will show up as a removable device.
-Your training data is in the Workout folder.
+ devices. To get the training just connect the device using the supplied
+USB cable to your computer and the device will show up as a removable device.
+Your training data is in the Workout folder.
</para>
<para>
<userinput>
-<para>\r
- This <ulink url="http://www.mglavionics.co.za/">MGL Avionics</ulink> format holds waypoints or routes. This routes can be loaded by the MGL Stratomaster Enigma EFIS series (\r
-<productname>Enigma</productname>, \r
-<productname>Odyssey</productname>, \r
-<productname>Voyager</productname>, \r
-<productname>Explorer</productname>). \r
-</para>\r
-<para>\r
- The format is designed for microcontrollers. The use is free for any non-military \r
- application. You can find a detailed description in the <ulink url="http://www.mglavionics.co.za/Docs/Enigma%20Waypoint%20format.pdf">MGL Documentation</ulink>.\r
-</para>\r
+<para>
+ This <ulink url="http://www.mglavionics.co.za/">MGL Avionics</ulink> format holds waypoints or routes. This routes can be loaded by the MGL Stratomaster Enigma EFIS series (
+<productname>Enigma</productname>,
+<productname>Odyssey</productname>,
+<productname>Voyager</productname>,
+<productname>Explorer</productname>).
+</para>
+<para>
+ The format is designed for microcontrollers. The use is free for any non-military
+ application. You can find a detailed description in the <ulink url="http://www.mglavionics.co.za/Docs/Enigma%20Waypoint%20format.pdf">MGL Documentation</ulink>.
+</para>
-<para>\r
- The <ulink url="http://www.mglavionics.co.za/">MGL Avionics</ulink> format holds waypoints or routes. These routes can be loaded by the MGL Stratomaster Enigma EFIS series (\r
-<productname>Enigma</productname>, \r
-<productname>Odyssey</productname>, \r
-<productname>Voyager</productname>, \r
-<productname>Explorer</productname>). \r
-</para>\r
-<para>\r
- The format is designed for microcontrollers. The use is free for any non-military application. You can find a detailed description in the <ulink url="http://www.mglavionics.co.za/Docs/Enigma%20Waypoint%20format.pdf">MGL Documentation</ulink>.\r
-</para>\r
+<para>
+ The <ulink url="http://www.mglavionics.co.za/">MGL Avionics</ulink> format holds waypoints or routes. These routes can be loaded by the MGL Stratomaster Enigma EFIS series (
+<productname>Enigma</productname>,
+<productname>Odyssey</productname>,
+<productname>Voyager</productname>,
+<productname>Explorer</productname>).
+</para>
+<para>
+ The format is designed for microcontrollers. The use is free for any non-military application. You can find a detailed description in the <ulink url="http://www.mglavionics.co.za/Docs/Enigma%20Waypoint%20format.pdf">MGL Documentation</ulink>.
+</para>
<para>
- This format reads and writes GPS information embedded in
- <ulink url="http://www.exif.org">EXIF</ulink>,
+ This format reads and writes GPS information embedded in
+ <ulink url="http://www.exif.org">EXIF</ulink>,
the Exchangeable Image Format, data. EXIF is a standardized method
of encoding data in pictures such as JPEG, TIFF, and WAV and is frequently
used by mobile phones with cameras and cameras with built-in GPS.
-<para>
+<para>
This format is for the .map files produced by the F90G automobile
Digital Video Recorder (DVR) when recording videos. The files are
<para>
-This format supports Garmin FIT activity files, defined as part
-of the ANT standard. These are generated by newer Garmin
+This format supports Garmin FIT activity files, defined as part
+of the ANT standard. These are generated by newer Garmin
devices like the ForeRunner 110.
</para>
-
-
+
+
<para> This was a requested <link linkend="fmt_csv">CSV format</link>, and is <emphasis>not</emphasis> the proprietary
binary format used by <ulink url="http://www.fugawi.com">Fugawi</ulink>. Like any other CSV format, GPSBabel
cannot read tracks in this format, but converting a track into it and
<para>
<ulink url="http://www.fugawi.com/">http://www.fugawi.com/</ulink>
</para>
-
+
-<para>
+<para>
Support for the "Garmin GPS Database" format used by
- default in <productname>MapSource</productname> versions since release 6.0 of
+ default in <productname>MapSource</productname> versions since release 6.0 of
that product. By default GPSBabel creates
gdb files of version 2. Version 2 is used in Mapsource 6.3 and 6.5. This format
is also used by <productname>Garmin BaseCamp</productname> for Mac and Windows.
</para>
-<para>
+<para>
Garmin GPS database is an undocumented file format. The
basic info for this module came from the existing MapSource
conversion code.
</para>
-
+
<para>
This format supports the <ulink url="http://www.geocaching.com">Geocaching.com</ulink>/<ulink url="http://www.easygps.com">EasyGPS</ulink> ".loc" format. This format
-was created specifically for Geocaching.com and is not the same as the
-standard EasyGPS .loc format. See the <link linkend="fmt_easygps">EasyGPS</link>
+was created specifically for Geocaching.com and is not the same as the
+standard EasyGPS .loc format. See the <link linkend="fmt_easygps">EasyGPS</link>
or <link linkend="fmt_gpx">GPX</link> formats for more general EasyGPS support.
</para>
<para>
-This is a simple XML-based format containing only very basic information
-about geocaches. If you can use the <link linkend="fmt_gpx">GPX</link>
+This is a simple XML-based format containing only very basic information
+about geocaches. If you can use the <link linkend="fmt_gpx">GPX</link>
format from Pocket Queries instead, you should consider doing so as it is a much richer format.
</para>
<para>
-We have a separate page describing how to <ulink url="/tips/browser.html">send from Geocaching.com pages to GPS</ulink>
+We have a separate page describing how to <ulink url="/tips/browser.html">send from Geocaching.com pages to GPS</ulink>
</para>
This module supports a subset of the <ulink url="http://geojson.org/">GeoJSON</ulink> format.
</para>
<para>
-GeoJSON is a poor fit for GPSBabel's internal data structures as GPSBabel
-was designed more around common GPS features (waypoints, tracks, routes)
+GeoJSON is a poor fit for GPSBabel's internal data structures as GPSBabel
+was designed more around common GPS features (waypoints, tracks, routes)
than about GIS-style concepts like MultiPolygons or Geometry Collections.
In reality, for all but the most simple uses (such as converting a format
that GPSBabel supports well to something like Leaflet, you should not expect
high fidelity transfers through this format.
</para>
<para>
-Waypoints are mapped to a FeatureCollection of Points.
+Waypoints are mapped to a FeatureCollection of Points.
The properties for name and description are written, where available.
Tracks are converted to a LineString.
MultiPoint are converted to Waypoints.
MultiLineString are converted to tracks.
</para>
<para>
-The potentially nested/recursive nature of GeoJSON in general would be
+The potentially nested/recursive nature of GeoJSON in general would be
an awkward implementation.
</para>
<para>
popular product in Germany.
</para>
<para>
- GPSBabel has full support for version 1.0 of this file format.
+ GPSBabel has full support for version 1.0 of this file format.
</para>
<para>
- We can also read some GPS data (including coordinates) from version 2.5. But
- it seems, that this newer version no longer stores time stamps. This can be
+ We can also read some GPS data (including coordinates) from version 2.5. But
+ it seems, that this newer version no longer stores time stamps. This can be
a problem when converting to other formats or if you want to use our track filter.
</para>
<para>
- Overlay files used by <productname>Geogrid</productname>-Viewer has to be in ASCII format.
+ Overlay files used by <productname>Geogrid</productname>-Viewer has to be in ASCII format.
Make sure you save the files correctly.
</para>
<para>
converted to tracks, except they are grouped. In this case GPSBabel creates routes.
</para>
<para>
- During the creation of an overlay file, a circle will be added to each
+ During the creation of an overlay file, a circle will be added to each
position of a waypoint or a route.
</para>
<para>
This is the XML format used by the Garmin Logbook product
- that ships with Forerunner and Foretrex.
+ that ships with Forerunner and Foretrex.
As of early 2006, this program is apparently been discontinued in favor of
<link linkend="fmt_gtrnctr">Garmin Training Center</link>.
- See: <ulink url="http://www.garmin.com">http://www.garmin.com</ulink>
+ See: <ulink url="http://www.garmin.com">http://www.garmin.com</ulink>
</para>
-
+
-
-
+
+
<para> This format is designed to read the XML emitted when you
use the <ulink url="https://developers.google.com/maps/documentation/directions/">
Google Directions API</ulink>.
operating system, this shell script might be useful:
</para>
<programlisting format="linespecific"><![CDATA[
-#!/bin/sh
-FROM="233 S. Upper Wacker Dr, Chicago, IL"
-TO="1060 W. Addison St, Chicago, IL"
+#!/bin/sh
+FROM="233 S. Upper Wacker Dr, Chicago, IL"
+TO="1060 W. Addison St, Chicago, IL"
URL="http://maps.googleapis.com/maps/api/directions/xml"
wget -O - "$URL?origin=$FROM&destination=$TO&sensor=false" \
2>/dev/null >google_map.xml
gpsbabel -i googledir -f google_map.xml -o gpx -F google_map.gpx
]]></programlisting>
-
+
<para>
This is the 'gpl' format as used in DeLorme mapping
products. It is a track format and contains little more than the
- tracklog of a GPS that was attached while driving.
+ tracklog of a GPS that was attached while driving.
<ulink url="http://www.frontiernet.net/~werner/gps/">frontiernet.net</ulink>
</para>
-
+
-
-
+
+
<para>GpsDrive way.txt file format. A space separated format
file. Tested against GpsDrive v 1.30 found at <ulink url="http://www.gpsdrive.de">gpsdrive.de</ulink>.
Contributed by Alan Curry.</para>
-
+
-
-
+
+
<para>Format used by GpsDrive to save tracks. Like GPSDRIVE a
space separated format file. See above for a link to GpsDrive.
Contributed by Tobias Minich.</para>
-
+
<listitem><para>Humminbird's "h" GPX extensions.</para></listitem>
</itemizedlist>
</para>
-
+
<para>
-GPSBabel supports reading and writing of tracks in the .tcx
-format used by <productname>Garmin Training Center</productname> (GTC). GTC is the successor
-to Garmin's <productname>Logbook</productname> program for their workout units. It is a
+GPSBabel supports reading and writing of tracks in the .tcx
+format used by <productname>Garmin Training Center</productname> (GTC). GTC is the successor
+to Garmin's <productname>Logbook</productname> program for their workout units. It is a
free upgrade.
</para>
<para>
-GPSBabel can read GTC v1 and v2 files, and can write v2 files.
+GPSBabel can read GTC v1 and v2 files, and can write v2 files.
v2 files are most likely to have a .tcx extension. v1 files
typically have a .hst or .crs extension, depending on whether they
are in the "history" or "course" format.
what we support. GPSBabel deals in waypoints, tracks, and routes.
While we do record things like heart rate and temperature when we know
it, the fundamentals of Training Center are different. It deals in
-concepts like laps and calories, which are rather alien to GPSBabel
+concepts like laps and calories, which are rather alien to GPSBabel
and most of the formats we support. As such, while we can describe
the tracks pretty accurately, things like calories and heart zone
tracking are not supported. Some of the auxiliary data, such as
heart rate (not zone), cadence, and bicycling power are supported.
</para>
<para>
-One of the most useful things you can do with this format is to send
-.tcx files found on the web or elsewhere to any supported GPS
-unit. You will probably want to include the transform (rte=trk)
+One of the most useful things you can do with this format is to send
+.tcx files found on the web or elsewhere to any supported GPS
+unit. You will probably want to include the transform (rte=trk)
and simplify filters in this process. For example,
</para>
<para><userinput>
-gpsbabel -i gtrnctr -f somefile.tcx -x simplify,count=50
+gpsbabel -i gtrnctr -f somefile.tcx -x simplify,count=50
-x transform,rte=trk -r -o garmin -F usb:
</userinput></para>
<para>
<para>
This is the .gps format used by the Mac OS X applications
written by HikeTech. These include TopoDraw, Link2GPS, and GPSWrite.
- More information about these products can be found at
+ More information about these products can be found at
<ulink url="http://www.hiketech.com">hiketech.com</ulink>
</para>
-
+
-
-
+
+
<para> The Holux gm-100 (e-fox) gps receiver uses standard
compact flash cards. File formats were provided by Holux-Taiwan
<ulink url="http://www.holux.com.tw">holux.com</ulink> to the author.
</para>
<para> This format was contributed by Jochen Becker.
</para>
-
+
-
-
+
+
<para>HSA Systems Endeavour Navigator format - will import both
the old version 4.x binary files, and the newer XML based ones. Only
writes the new XML (5.0 and above) format. (use the .exp
extension)</para>
-
+
-<para>
+<para>
GPSBabel's HTML output generates a single HTML file of all of the
waypoints in the input file. It supports a number of Groundspeak GPX
extensions and filters out potentially harmful HTML from the
- input file while maintaining almost all of the source HTML formatting.
+ input file while maintaining almost all of the source HTML formatting.
This makes this format well suited for generating HTML to hand to programs
like Plucker for putting in a PDA and especially so for "paperless caching"
for Geocachers with pocket queries.
<para>
<userinput>gpsbabel -i gpx -f 12345.gpx -o html,stylesheet=green.css,encrypt -F 12345.html</userinput>
</para>
-
+
</simplelist>
</para>
<para>
- If you do "save all nav data" on the device, you'll get a
+ If you do "save all nav data" on the device, you'll get a
<filename>data.hwr</filename> and a <filename>000.ht</filename> file on the
flash card (on a 797 in the <filename>matrix</filename> directory).
</para>
tell it which ones to write. By default, you get a <filename>.hwr</filename>
file, to get a track (<filename>.ht</filename> file), use the
"humminbird-track" format.
-</para>
+</para>
<para>
<informalfigure><mediaobject><imageobject>
<imagedata fileref="humminbird.png" format="PNG"/>
- </imageobject> </mediaobject> </informalfigure>
+ </imageobject> </mediaobject> </informalfigure>
</para>
<para>
Note:<filename>.dat</filename> files are read-only, they only make sense
<member>797c2i SI</member>
</simplelist>
(They should all work, but this is the only one tested so far.)
- </para>
+ </para>
<para>
Known limits:
<simplelist>
<para>
- This is the format used by the software that comes with the
+ This is the format used by the software that comes with the
<ulink url="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81290">
Transystem i-Blue757 Pro GPS
</ulink>.
- It is very similar to the <link linkend="fmt_iblue747">iBlue747</link>
+ It is very similar to the <link linkend="fmt_iblue747">iBlue747</link>
format, apart from the date format being reversed.
</para>
<para>
- The csv log file can be extracted from the GPS receiver using
+ The csv log file can be extracted from the GPS receiver using
the BT747 software available from <ulink url="http://www.bt747.org"></ulink>
</para>
<para>
-This format supports IGN Rando track files. IGN Rando is a program mainly
-used in France for Topo maps. The files are XML based and are "windows-1252"
+This format supports IGN Rando track files. IGN Rando is a program mainly
+used in France for Topo maps. The files are XML based and are "windows-1252"
encoded. Trackpoints do not have time stamps.
</para>
-
+
<para>
igo2008_poi supports POI files from <productname>Nav N Go iGO 8 Europe</productname>.
- This is a GPS Navigation Software for <productname>Windows Mobile</productname> based
+ This is a GPS Navigation Software for <productname>Windows Mobile</productname> based
PDA devices and Smartphones.
</para>
route-planning software with a 3-dimensional environment.
</para>
<para>
- The project files are XML based and we can read the main GPS items (names and coordinates).
+ The project files are XML based and we can read the main GPS items (names and coordinates).
For an output these files are too complex.
</para>
-<para>
-KML, the Keyhole Markup Language format, was used by Keyhole and is used by
-<ulink url="http://earth.google.com">Google Earth</ulink>.
+<para>
+KML, the Keyhole Markup Language format, was used by Keyhole and is used by
+<ulink url="http://earth.google.com">Google Earth</ulink>.
</para>
-<para>There are concepts in KML that GPSBabel can't support very well on
+<para>There are concepts in KML that GPSBabel can't support very well on
read because they don't map well into other programs. For example, KML has
-ideas of camera views and names and descriptions can have arbitrarily
+ideas of camera views and names and descriptions can have arbitrarily
complicated HTML in them. KML files may have tiered "Styles" which
can identify sizing info and URLs of associated icons. Reading such
files with GPSBabel - even if your goal it to write it back out as KML - can often
In general, GPSBabel's KML writer is relatively strong. GPSBabel handles simple KML on read fairly well, but if you're dealing with handcrafted KML that uses extensive features that have no analog in other formats like nested folders, ringgeometry, camera angles, and such, don't expect GPSBabel to do well with them on read.
</para>
<para>
- Google Earth 4.0 and later have a feature that can surprise users of this
+ Google Earth 4.0 and later have a feature that can surprise users of this
format. Earth's "time slider" feature controls what timestamped data
- gets displayed. If you're using data that has timestamps (e.g. GPX
+ gets displayed. If you're using data that has timestamps (e.g. GPX
points that contain time or almost any track data) this will be important
to you. The time slider defaults to the far left position and fully closed.
This means that only the first data point will be displayed. You can
</para>
<para>
<ulink url="http://www.kompass.at">Kompass</ulink> is a publishing company from Austria.
- If you want to get more information about DAV, the German alpine association,
+ If you want to get more information about DAV, the German alpine association,
and if you are familiar with the german language, please have a look at their <ulink url="http://www.alpenverein.de">homepage</ulink>.
</para>
<para>Support for Kartex 5 trackfiles. For more info see <link linkend="fmt_kwf2">kwf2</link>.</para>
-
+
-
-
- <para>Support for Kartex 5 waypoint files. Kartex is a Swedish
- map and GPS positioning system. GPSBabel can read and write
- files from Kartex 4 and 5 with WGS84 coordinates. UTM or
+
+
+ <para>Support for Kartex 5 waypoint files. Kartex is a Swedish
+ map and GPS positioning system. GPSBabel can read and write
+ files from Kartex 4 and 5 with WGS84 coordinates. UTM or
Swedish grid are not supported.
</para>
-
+
-<para>
+<para>
This format supports
<ulink url="http://sw.nokia.com/id/9001c8de-c19e-41a0-87d3-5be4297e4d4c/S60_Platform_Landmarks_Exchange_Specification_v1_0_en.pdf">
Nokia Landmark Exchange (LMX) files</ulink> used by several Nokia phones.
<para>
- The Holux m241 is a small datalogger using the MTK chipset, with
- a couple small differences in the binary format. In its default
+ The Holux m241 is a small datalogger using the MTK chipset, with
+ a couple small differences in the binary format. In its default
configuration, it can store ~100000 trackpoints with very limited
- data; to configure extended logging you can use the BT747 open
- source software
+ data; to configure extended logging you can use the BT747 open
+ source software
<ulink url="http://bt747.wiki.sourceforge.net">bt747</ulink>
Waypoint storage is possible only if "recording reason" (RCR) is enabled in the settings.
</para>
<para>
- Holux GPSport 245 is a datalogger with display suitable for cycling, walking and running.
- It can store ~200k trackpoints with limited data. The m241 and m241-bin format is
+ Holux GPSport 245 is a datalogger with display suitable for cycling, walking and running.
+ It can store ~200k trackpoints with limited data. The m241 and m241-bin format is
able to automatically detect GPSport 245 data and handle the differences from Holux M-241 devices.
Note: GP245 does not log any quality of the position.
</para>
<member>Explorist XL</member>
</simplelist>
</para>
-
+
<para>
This format is used for both the serial protocol used on the
devices with serial ports such as Map330 and Meridian and for
- the files stored either in either the unit's internal memory
- (Explorist 210, Explorist 400, Explorist 500, Explorist 600,
+ the files stored either in either the unit's internal memory
+ (Explorist 210, Explorist 400, Explorist 500, Explorist 600,
Explorist XL) or on removable memory.
-</para>
+</para>
<para>
If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0")
to be read or written, GPSBabel will use serial protocol. Specifying
<para>
The RoadMate family of products is not supported.
</para>
-
+
<para>
This format is used for both the serial protocol used on the
devices with serial ports such as Map330 and Meridian and for
- the files stored either in either the unit's internal memory
+ the files stored either in either the unit's internal memory
(Explorist 210, 400, 500, 600, XL) or on removable memory.
-</para>
+</para>
<para>
If you specify a serial port for the file (.e.g. "COM1", "/dev/ttyS0")
to be read or written, GPSBabel will use serial protocol. Specifying
<para>
This is the SD card format used by the <ulink url="http://www.magellangps.com">Magellan</ulink> Explorist 400,
- Explorist 500, Explorist 600, and Explorist XL and internally on those devices plus the
+ Explorist 500, Explorist 600, and Explorist XL and internally on those devices plus the
Explorist 210. Stored waypoints are identical to the <link linkend="fmt_magellan">Magellan SD format</link>
- used by Meridian, but the newer models allow longer waypoint names. Routes are
+ used by Meridian, but the newer models allow longer waypoint names. Routes are
subtly different.
</para>
-<para>
- You should name any file containing waypoints created with
+<para>
+ You should name any file containing waypoints created with
this format with a ".upt" extension so the firmware can read it.
Similarly, routes should be named ".rte" and tracks should be
named ".log".
</para>
-
+
<para>
- <ulink url="http://www.mapking.com/en/">Mapking</ulink> provides a set of tools for GPS
- navigation. The location of distributed maps is mainly in Asia, so the software seems
- not (yet) well known in Europe or US. Some of the GPS tools (e.g. Mapking 2007 for Windows Mobile)
+ <ulink url="http://www.mapking.com/en/">Mapking</ulink> provides a set of tools for GPS
+ navigation. The location of distributed maps is mainly in Asia, so the software seems
+ not (yet) well known in Europe or US. Some of the GPS tools (e.g. Mapking 2007 for Windows Mobile)
can also be used to write waypoints and save them under the .tr7 format which can be translated by GPSBabel.
</para>
This format is the Mapbar navigation programs used on phones such as
the Sonim XP3300 popular in China.
The files are found on the sd card in /mapbar/userdata/tracks.
- This format just logs track point by latitude and longitude; no time
+ This format just logs track point by latitude and longitude; no time
information is available.
</para>
<para>
</para>
<para>
The following devices of using mapbar navigation are supported. Other
-devices with using mapbar navigation maybe be supported, but not have
+devices with using mapbar navigation maybe be supported, but not have
not been tested:
<simplelist columns="1">
<member>Sonim Xp3300(China version)</member>
mapconverter application.
</para>
<para>
-Mapconverter is an application used to create userland maps and map data for
+Mapconverter is an application used to create userland maps and map data for
Mapopolis.com's Mapopolis program. The mapconverter format is essentially
waypoint data prepared in a format that the mapconverter application will
accept.
<listitem>
<para>
GPSBabel will write the name of its own output file in the output file
- it creates as the input for Mapconverter. Mapconverter will replace
+ it creates as the input for Mapconverter. Mapconverter will replace
the extension of this filename with ".pdb".
</para>
</listitem>
<para>
Mapconverter is no longer available from the Mapopolis website. If you
need a copy of mapconverter, ask on your local GPS Software discussion
- forum and I'm sure someone will have it. As far as I know, It was never
+ forum and I'm sure someone will have it. As far as I know, It was never
actually acknowledged/supported by Mapopolis to begin with.
</para>
</listitem>
<para>
-Serial download protocol for GPS data loggers called "miniHomer".
+Serial download protocol for GPS data loggers called "miniHomer".
These loggers are based on Skytraq Venus 5 and Venus 6 chipsets, but with modified firmware.
-The miniHomer logger has five POI (or better: Point-to-Return, PTR?), which can be set programatically. The miniHomer module in gpsbabel is an extension of the skytraq module.
+The miniHomer logger has five POI (or better: Point-to-Return, PTR?), which can be set programatically. The miniHomer module in gpsbabel is an extension of the skytraq module.
</para>
<para>
<tgroup cols="4">
<thead>
<row>
- <entry>Manufacturer</entry>
- <entry>Model</entry>
- <entry>USB (baud)</entry>
+ <entry>Manufacturer</entry>
+ <entry>Model</entry>
+ <entry>USB (baud)</entry>
<entry>Bluetooth (baud)</entry>
</row>
</thead>
<para><userinput>gpsbabel -i miniHomer,erase,no-output -f /dev/ttyUSB0</userinput></para>
</example>
-<para>miniHomer has five POI called Home, <emphasis>Car</emphasis>, <emphasis>Boat</emphasis>, <emphasis>Heart</emphasis>, <emphasis>Bar</emphasis>. You can set the lla
-(Latitude, Longitude, Altitude) for each of the POI. The format is
+<para>miniHomer has five POI called Home, <emphasis>Car</emphasis>, <emphasis>Boat</emphasis>, <emphasis>Heart</emphasis>, <emphasis>Bar</emphasis>. You can set the lla
+(Latitude, Longitude, Altitude) for each of the POI. The format is
<emphasis><name>=<lat>:<lng>[:<alt>]</emphasis>
Once the according POI symbol is selected on miniHomer, the display shows you the direction and distance to the POI.
</para>
gpsbabel -i miniHomer,Car=36.790145:-6.352898,Home=-3.066667:37.359167:5895 -f /dev/ttyUSB0 -o gpx -F out.gpx
</userinput>
Sets the Car/Home symbols' latitude longitude and altitude.
- If you select the Car/Home symbol on miniHomer, the display will show the direction and distance to
+ If you select the Car/Home symbol on miniHomer, the display will show the direction and distance to
this location as soon as it has a satellite fix.
</para>
</example>
which causes errors, please provide it [mailto:gpsbabel-misc@lists.sourceforge.net].
</para>
<para>
- More information can be found at the
+ More information can be found at the
<ulink url="http://www.memory-map.com/">Memory-Map</ulink> site.
</para>
<para>
The <productname>MotoACTV</productname> smart watch creates csv
format files. GPSBabel can read and write these files through
-the xcsv format when using the included motoactv.style specification.
+the xcsv format when using the included motoactv.style specification.
</para>
<para>
The specific format of the csv file has changed over time, to
It has been tested with <productname>Transystem i-Blue 747</productname> but other devices should
work as well (Qstarz BT-Q1000, iTrek Z1, ...)
</para><para>
-All position items (including button push) will be listed as trackpoints in the output.
-Log items due to button push are presented as waypoints.
-In theory we would not add waypoints to the list of trackpoints. But as the MTK logger restart the
+All position items (including button push) will be listed as trackpoints in the output.
+Log items due to button push are presented as waypoints.
+In theory we would not add waypoints to the list of trackpoints. But as the MTK logger restart the
log session from the button press we would loose a trackpoint unless we include/duplicate it.
</para>
<para>
- This format is the serial download protocol for the MTK chips.
- Mediatek's MT3301/3179 (MTKv1) and MT3318 (MTKv2) chips are used
- in a large number of products sold under different names.
+ This format is the serial download protocol for the MTK chips.
+ Mediatek's MT3301/3179 (MTKv1) and MT3318 (MTKv2) chips are used
+ in a large number of products sold under different names.
</para>
<para>
- Many GPS products, especially of the data logger variety, expose
- the Mediatek protocol to the user via USB. Some modify Mediatek's
- protocol in minor ways, but the core protocol is very commonly
- seen in loggers.
+ Many GPS products, especially of the data logger variety, expose
+ the Mediatek protocol to the user via USB. Some modify Mediatek's
+ protocol in minor ways, but the core protocol is very commonly
+ seen in loggers.
</para>
<para>
- The <link linkend="fmt_m241">Holux M-241 and GPSport 245</link>
- are examples of a device using an incompatible variation of the MTK
+ The <link linkend="fmt_m241">Holux M-241 and GPSport 245</link>
+ are examples of a device using an incompatible variation of the MTK
protocol.
</para>
<para>
The following products are known or are expected to work with this module.
-As the products are typically very low cost, they tend to have a short
-product life cycle and are often imported to different areas under
+As the products are typically very low cost, they tend to have a short
+product life cycle and are often imported to different areas under
different names. Keeping
track of the list is difficult. Often the "same" GPS is sold in different
-plastic or with different Windows software or different options such as
+plastic or with different Windows software or different options such as
compass or motion sensors or charging cables with different model numbers.
If you can confirm success with others, please share with us.
</para>
-
+
<table id="mtk_devices">
<title>Devices supported by MTK module</title>
<tgroup cols="3">
<thead>
<row>
- <entry>Product</entry>
- <entry>Confirmed to work</entry>
- <entry>Notes</entry>
+ <entry>Product</entry>
+ <entry>Confirmed to work</entry>
+ <entry>Notes</entry>
</row>
</thead>
<tbody>
<row>
- <entry>iBlue 821</entry>
- <entry>Yes</entry>
- <entry>Available from <ulink url="http://www.semsons.com/i821ulblgpsr.html">Semsons</ulink></entry>
+ <entry>iBlue 821</entry>
+ <entry>Yes</entry>
+ <entry>Available from <ulink url="http://www.semsons.com/i821ulblgpsr.html">Semsons</ulink></entry>
</row>
<row>
- <entry>iBlue 747, 747A+</entry>
- <entry>Yes</entry>
- <entry>Available from <ulink url="http://www.semsons.com/i74blgpsdalo.html">Semsons</ulink></entry>
+ <entry>iBlue 747, 747A+</entry>
+ <entry>Yes</entry>
+ <entry>Available from <ulink url="http://www.semsons.com/i74blgpsdalo.html">Semsons</ulink></entry>
</row>
<row>
- <entry>QStarz BT-1000, BT-Q1000X, BT-1000eX</entry>
- <entry>Yes</entry>
- <entry></entry>
+ <entry>QStarz BT-1000, BT-Q1000X, BT-1000eX</entry>
+ <entry>Yes</entry>
+ <entry></entry>
</row>
<row>
- <entry>iTrek Z1</entry>
- <entry></entry>
- <entry></entry>
+ <entry>iTrek Z1</entry>
+ <entry></entry>
+ <entry></entry>
</row>
</tbody>
</tgroup>
<para>
The Mediatek chip offers a native serial port. Data logger designers
frequently pair this with commodity USB/Serial converter internally. So
- these devices typically look like Prolific, FTDI, or Silab usb/serial
- devices to the host OS. You'll need drivers for that whatever chip
+ these devices typically look like Prolific, FTDI, or Silab usb/serial
+ devices to the host OS. You'll need drivers for that whatever chip
your product uses for your operating system. For the "A+ GPS Recorder",
the <ulink url="http://www.silabs.com/products/mcu/pages/usbtouartbridgevcpdrivers.aspx">Silicon Labs CP210x chip</ulink> is used. On OS/X, you'll get
awesome device names like /dev/cu.usbmodem1d13410 - fortunately, our GUI
makes that multiple choice so you don't have to guess.
</para>
<para>
- Downloaded data will be stored in data.bin file in the current
+ Downloaded data will be stored in data.bin file in the current
directory together with the chosen output format. This is a rather
uncommon feature in GPSBabel's formats and is likely to change in future
versions.
<title>Command showing MTK download track and waypoints and erase on Linux</title>
<para><userinput>gpsbabel -t -w -i mtk,erase -f /dev/ttyUSB0 -o gpx -F out.gpx</userinput></para>
</example>
-
+
<para>
- For more info and tweaks on MTK based loggers:
+ For more info and tweaks on MTK based loggers:
<ulink url="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81990">MTK Tips and Tweaks</ulink> and
<ulink url="http://www.gpspassion.com/forumsen/topic.asp?TOPIC_ID=81315">iBlue 747 Logger</ulink>
For info about the used log format, see
<ulink url="http://spreadsheets.google.com/pub?key=pyCLH-0TdNe-5N-5tBokuOA&gid=5">MTK binary format</ulink>
</para>
<para>
-Most of the loggers cannot receive bluetooth commands; they can only send
+Most of the loggers cannot receive bluetooth commands; they can only send
data. Since GPSBabel needs to send commands to the GPS device it won't
work. Download the data using the USB cable instead.
</para>
<para>
-This format is a protocol supports the MediaTek MT3339, a GPS
-chipset that shipped around 2011 that has internal logging capability.
-It is the
-core of at least two GPS modules, including the
+This format is a protocol supports the MediaTek MT3339, a GPS
+chipset that shipped around 2011 that has internal logging capability.
+It is the
+core of at least two GPS modules, including the
GlobalTop PA6H and the Fastrax IT530. The GlobalTop PA6H module is in
turn the heart of the Adafruit "Ultimate" GPS breakout board, popular
in the Arduino "maker" world.
-
-
+
+
<para>Maptech Exchange Format - Another CSV format file. This
format complies with (at least) Maptech Terrain Navigator, Terrain
Professional, Take a Hike, and ExpertGPS import/export MFX.
Contributed by Alex Mottram.</para>
-
+
</para>
<para>
To actually manipulate the file on the unit, use a USB cable or SD card
- reader and work with <filename>MN6\Settings\Favorites.storage</filename>
+ reader and work with <filename>MN6\Settings\Favorites.storage</filename>
The waypoints are be created with a minimal amount of data; the unit will
fill in the other fields on use. The other fields appear to be data the
unit infers, such as nearby streets.
</para>
<para>
- Note that this is the waypoint/placemark format (.storage) and not the
+ Note that this is the waypoint/placemark format (.storage) and not the
route file format (.rte, .mn4) that is used by routes.
</para>
<para>
GPSBabel supports the Navilink protocol used by the
- <ulink url="http://www.locosystech.com/product.php?zln=en&id=5">Locosys GT-11</ulink>
+ <ulink url="http://www.locosystech.com/product.php?zln=en&id=5">Locosys GT-11</ulink>
and
<ulink url="http://www.locosystech.com/product.php?zln=en&id=30">GT-31</ulink>
GPS receivers. These are sold under a variety of names including:
<para>
To access the device using the serial protocol over USB the
device needs to be in Navilink mode, which can be activated
- from the main menu of the device. This device uses a Prolific
- PL2303 USB/Serial adapter internally and that's how it will
+ from the main menu of the device. This device uses a Prolific
+ PL2303 USB/Serial adapter internally and that's how it will
present itself to the host operating system. You thus need
USB drivers for the PL2303, such as those from the 'Download'
section of
This format reads summary files from <productname>NetStumbler</productname>
<productnumber>0.4</productnumber> or <productname>MacStumbler</productname>.
</para>
-<para>
+<para>
The default behavior when creating waypoints is to use the SSID for
the short name, and information about the access point for the
description. When the SSID is not unique, is not available, or
-consists of whitespace, a short name is synthesized.
+consists of whitespace, a short name is synthesized.
</para>
-<para>
+<para>
Different icons are assigned to encrypted,
non-encrypted, stealth, and non-stealth access points; these may be
-changed with options.
+changed with options.
</para>
<para>
<ulink url="http://www.netstumbler.com/">NetStumbler</ulink>
</para>
<para>
-<ulink url="http://www.macstumbler.com/">MacStumbler</ulink>
+<ulink url="http://www.macstumbler.com/">MacStumbler</ulink>
</para>
-
-
+
+
<para>This is a CSV format from the National Imagery and Mapping
Agency.</para>
-
+
-
-
-<para> This format is the file representation of the NMEA
+
+
+<para> This format is the file representation of the NMEA
(National Marine Electronics Association) 0183
log and waypoint format for GPS devices. Some hardware and software
that work with NMEA-0183 formatted data include:
<member>
Sony GPS_CS1
</member>
-</simplelist>
+</simplelist>
<para>
-This module also supports <link linkend="tracking">realtime tracking</link>
-which allows realtime position reports from a GPS, such as one connected
+This module also supports <link linkend="tracking">realtime tracking</link>
+which allows realtime position reports from a GPS, such as one connected
serially, over Bluetooth, or a USB module emulating a serial port, to be used
with selected output formats. Just specify an input file that is the device
name such as COM1: for Windows or a device-dependent name like
-/dev/cu.usbserial for Mac or /dev/ttyUSB0 for Linux. (Note that serial
+/dev/cu.usbserial for Mac or /dev/ttyUSB0 for Linux. (Note that serial
device names vary on Mac and Linux.)
</para>
<para>
-<para>
+<para>
Tab separated export-all (except geocaching data) file
format. Intended to serve as source for number-processing
applications like OpenOffice, Ploticus and others. Tab was chosen as
<para>
-Because the format supports only one route, this option may be used
-on output to select a single route from a collection of
-routes read from a more expressive format. If you have, say, a
+Because the format supports only one route, this option may be used
+on output to select a single route from a collection of
+routes read from a more expressive format. If you have, say, a
<link linkend="fmt_gpx">gpx</link> file that contains two routes, you may
use this option to write them one at a time to individual files.
</para>
<para>
This route specifies the name of the route. This is particularly useful if
-the route came from an input format that did not support named routes, but
+the route came from an input format that did not support named routes, but
it may also be used to rename a route.
</para>
<para>
-This option instructs GPSBabel to use a different value for the radius of
-the earth when converting between the Mercator projection and geographic
+This option instructs GPSBabel to use a different value for the radius of
+the earth when converting between the Mercator projection and geographic
coordinates. The default value is 6371000.0 meters.
</para>
<para>
<para>
This option will add the icon description to the end of the waypoint
description on output. This can be useful if the icon is used to convey
-important information about the waypoint. For example, the icon might be
+important information about the waypoint. For example, the icon might be
"found geocache" or "unfound geocache"; it might be useful to know that when
looking at a list of icons in Cetus.
</para>
<para>
-This 1/0 option, defaulting to if not provided, tells GPSBabel to
-use its own logic when sending data it can deduce is a geocache to
+This 1/0 option, defaulting to if not provided, tells GPSBabel to
+use its own logic when sending data it can deduce is a geocache to
the device. If false, any icon data present in the source data will
be used instead. If you've taken control of the icon data, you are
- responsible for providing valid icons; GPSBabel will make no attempt
+ responsible for providing valid icons; GPSBabel will make no attempt
to purify what gets sent.
</para>
<para>
- When set to true, this places the "HINT:" entry from a geocaching.com
+ When set to true, this places the "HINT:" entry from a geocaching.com
pocket query at the end of the screen (scroll up for quick access) like
Cache Register and Topo7 do instead of at the top as Topo8 does.
</para>
<para>
- When set to true, this places the "HINT:" entry from a geocaching.com
+ When set to true, this places the "HINT:" entry from a geocaching.com
pocket query at the end of the screen (scroll up for quick access) like
Cache Register and Topo7 do instead of at the top as Topo8 does.
</para>
<para>
- When set to true, this includes Groundspeak logs from GPX pocket queries
+ When set to true, this includes Groundspeak logs from GPX pocket queries
when writing to DeLorme devices that support the extended features introduced
in firmware version 2.5 for the PN-40 and PN-30 and in 1.6 for the PN-20.
</para>
<para>
- Use long waypoint notes, overriding the built-in version check (which is
+ Use long waypoint notes, overriding the built-in version check (which is
reverse engineered) that tests if the unit can handle the waypoint comments
longer than 800 bytes.
</para>
<para>
This option will probably go away in time as most units get upgraded to
- the capabilities of the 2.5 version of the PN-40 and PN-30 or version 1.6
+ the capabilities of the 2.5 version of the PN-40 and PN-30 or version 1.6
for the PN-20.
</para>
<para>
- When present on the command line and sending waypoints (either explicitly
+ When present on the command line and sending waypoints (either explicitly
via -w or as the default), this will erase
all waypoints in the receiver before sending the new ones.
</para>
</para>
<para>
The known variants of Tracklog 'digital mapping' files supports only
- one track per file. If you have more than one track in source
- (f.e MapSource and many others can do such heavy things), you
- can specify which track should by used for the conversion.
+ one track per file. If you have more than one track in source
+ (f.e MapSource and many others can do such heavy things), you
+ can specify which track should by used for the conversion.
</para>
<para>
The default index is 1 (the first track of a possible list of tracks).
<para>
Frame means the maximum time difference that we accept between the EXIF time information
- of a picture and the timestamp of a track-, route- and waypoint used for tagging.
+ of a picture and the timestamp of a track-, route- and waypoint used for tagging.
Without this option the maximum time frame is 10 seconds.
</para>
<para>
</para>
<para>
-At the end of the transfer, baud rate is switched to back to the default
-of 9600. If connection breaks, the unit stucks at high baud rate, a power
+At the end of the transfer, baud rate is switched to back to the default
+of 9600. If connection breaks, the unit stucks at high baud rate, a power
cycle reverts to original state.
</para>
<para>
Because this feature uses undocumented Garmin protocols, it may or may
-not work on your device. The author reported success with
+not work on your device. The author reported success with
eTrex Vista, GPSMAP 76s, and GPS V, but it seems likely to be problematic
on older units and may be more problematic for writing to the device than
reading data from the device.
<para>
- This option is closely related to the 'category' option. While category
+ This option is closely related to the 'category' option. While category
allows you to choose a single category that waypoints should appear in,
this options allows you to specify a bitmask to be used for the category.
Options may be specified in either decimal or hex.
<userinput>
gpsbabel -i gpx -f PocketQuery.gpx -o garmin,bitcategory=0x8001 -F usb:
</userinput>
-
+
</para>
</example>
<para>
This option is experimental and was added to solve a very specific problem.
- Certain Garmin units (the original black and white Vista is known to have
+ Certain Garmin units (the original black and white Vista is known to have
this) will sometimes scramble their clock crazy far into the future (like
- 2066). When this happens, the GPS itself may or may not work and
+ 2066). When this happens, the GPS itself may or may not work and
later conversations with GPSBabel may fail as the time overflows the
documented range. The use of <option>resettime</option> brings the GPS's internal clock
back close enough to reality that the GPS itself can then "fix" it when
-<para>This options controls whether spaces are allowed in generated
+<para>This options controls whether spaces are allowed in generated
smart names when using the '-s' option.</para>
values are in kilometers per hour.
</para>
<para>
- Proximity distance is also supported by <link linkend="fmt_gpx">GPX</link>, <link linkend="fmt_gdb">Garmin GDB</link>, <link linkend="fmt_ozi">OZI Explorer</link>,
+ Proximity distance is also supported by <link linkend="fmt_gpx">GPX</link>, <link linkend="fmt_gdb">Garmin GDB</link>, <link linkend="fmt_ozi">OZI Explorer</link>,
and <link linkend="fmt_unicsv">Universal CSV</link>.
</para>
<para>
<para>
If you're starting from images in another format, you may need to
use another tool like Gimp or ImageMagick's convert to get the image
- into one of the above formats to avoid errors about "Unsupported color
+ into one of the above formats to avoid errors about "Unsupported color
depth".
</para>
<para>
- Not all devices can support all color depths. GPSBabel (and its
+ Not all devices can support all color depths. GPSBabel (and its
developers) have no way of knowing what is supported on any given model
so some experimentation may be necessary on your part. It was reported
that a Nuvi 3790, for example, will read the POIs only if they use 8BPP.
</para>
<para>
- A color value of 0xFF00FF (blue=255, green=0, red=255),
+ A color value of 0xFF00FF (blue=255, green=0, red=255),
also called "Magenta", can be used for transparent areas.
</para>
<para>
<title>Example for specifying language with a garmin points of interest dual language file.</title>
<para>
<userinput>
- gpsbabel -i garmin_gpi,languagecode=EN -f reference/spb_metro_norm.gpi
+ gpsbabel -i garmin_gpi,languagecode=EN -f reference/spb_metro_norm.gpi
</userinput>
could produce the following output:
<simplelist type="vert">
<tgroup cols="2">
<thead>
<row>
- <entry>Unit</entry>
- <entry>Description</entry>
+ <entry>Unit</entry>
+ <entry>Description</entry>
</row>
</thead>
<tbody>
<para>
- The Garmin units seem to use the creation timestamp of GPI files for internal purposes.
- In other words, if you load GPI files with same creation timestamp on your device,
+ The Garmin units seem to use the creation timestamp of GPI files for internal purposes.
+ In other words, if you load GPI files with same creation timestamp on your device,
strange things will happen, such as having missing or repeated POIs. With the sleep option, GPSBabel waits a given
number of seconds after the GPI file was written.
</para>
<tgroup cols="2">
<thead>
<row>
- <entry>Unit</entry>
- <entry>Description</entry>
+ <entry>Unit</entry>
+ <entry>Description</entry>
</row>
</thead>
<tbody>
<para>
-This option specifies the input and output format for the date. The format
+This option specifies the input and output format for the date. The format
is written similarly to those in Windows. An example format is "YYYY/MM/DD".
</para>
<para>
-This option specifies the datum to be used on output. Valid values for this
+This option specifies the datum to be used on output. Valid values for this
option are listed in <xref linkend="Datums" />.
</para>
<tgroup cols="4">
<thead>
<row>
- <entry># idx</entry>
- <entry>short</entry>
- <entry>file-header</entry>
+ <entry># idx</entry>
+ <entry>short</entry>
+ <entry>file-header</entry>
<entry>sample</entry>
</row>
</thead>
<para>
-This option specifies the input and output format for the time. The format
+This option specifies the input and output format for the time. The format
is written similarly to those in Windows. An example format is "hh:mm:ss xx".
</para>
<para>
This option specifies the local time zone to use when writing times. It
-is specified as an offset from Universal Coordinated Time (UTC) in hours.
+is specified as an offset from Universal Coordinated Time (UTC) in hours.
Valid values are from -23 to +23.
-</para>
+</para>
<para>
- This option is closely related to the 'category' option. While category
+ This option is closely related to the 'category' option. While category
allows you to choose a single category that waypoints should appear in,
this options allows you to specify a bitmask to be used for the category.
Options may be specified in either decimal or hex.
<userinput>
gpsbabel -i gpx -f PocketQuery.gpx -o gdb,bitscategory=0x8001 -F foo.gdb
</userinput>
-
+
</para>
</example>
<para>
-This option specifies the default category for gdb output. It should be a
+This option specifies the default category for gdb output. It should be a
number from 1 to 16.
</para>
<para>
-This option instructs GPSBabel to drop hidden (calculated) points from
+This option instructs GPSBabel to drop hidden (calculated) points from
routes when creating waypoints. These points are not converted to waypoints, but they are converted to route points.
</para>
-
+
<para>
- If this option is specified, GPSBabel drops all calculated route points,
+ If this option is specified, GPSBabel drops all calculated route points,
with exception of points with a description (i.e. "Make U-turns until you know where you are.").
- The priority of this option is higher than of the <option>via</option> and <option>dropwpt</option> options.
+ The priority of this option is higher than of the <option>via</option> and <option>dropwpt</option> options.
A value of 1 or y overwrites the <option>via</option> and <option>dropwpt</option> settings.
</para>
<example id="gdb_roadbook_option">
<para>
Because gdb internally creates a route AND a waypoint list, you have to drop all
waypoints and transform the route into waypoints in order to get a well ordered
- html output. We suggest these steps for all waypoint-only formats as html.
+ html output. We suggest these steps for all waypoint-only formats as html.
</para>
</example>
<para>
-This option instructs GPSBabel to drop hidden (calculated) points from
+This option instructs GPSBabel to drop hidden (calculated) points from
routes. These points are not converted to waypoints or route points.
</para>
-
+
<para>
-This option specifies the icon or waypoint type to write for each waypoint on
+This option specifies the icon or waypoint type to write for each waypoint on
output.
</para>
<para>
-If this option is specified, its value will be used for all waypoints, not
-just those that do not already have descriptions. That is, this option
+If this option is specified, its value will be used for all waypoints, not
+just those that do not already have descriptions. That is, this option
overrides any icon description that might be in the input file.
</para>
<para>
<para>
- This option, when set, reduces the amount of whitespace in the
+ This option, when set, reduces the amount of whitespace in the
generated GeoJSON. This reduces the size, especially when uncompressed,
but reduces the readability to humans.
</para>
<para>
The dump-file option is primarily for debugging is module. It lets you
provide a file which contains the raw stream of bytes coming from the
-device. This is useful for capturing device state to describe to a
+device. This is useful for capturing device state to describe to a
developer that can't actually access hte physical device as well as mocking
the entire device for automated regression testing.
</para>
<para>
<screen>
-<command>gpsbabel</command>
+<command>gpsbabel</command>
-i glboalsat,dump-file=<replaceable>gh625xt.bin</replaceable> -f <replaceable>/dev/ttyUSB0</replaceable>
</screen>
can be used to read the device and store its state in the file <filename>gh625xt.bin</filename>. That file can then be distributed and someone else can
read it with a command line:
<screen>
-<command> gpsbabel</command>
+<command> gpsbabel</command>
-i globalsat,input-is-dump-file=1 -f <replaceable>gh625xt.bin</replaceable> -o gpx -F <replaceable>test.gpx</replaceable>
</screen>
</para>
-<para>When this option is specified, GPSBabel will split
+<para>When this option is specified, GPSBabel will split
split the output into multiple files using the output filename
as a base. For example, if you specify an output file of 'mytrip',
<simplelist type="vert">
writing elevation values.
Precision is the number of digits after the decimal point. The default
precision is 3. We limit the number of places we write to improve the
-fidelity when round-tripping elevation, reduce file size, and reduce
-silliness in files caused by repeating decimals in insignificant
+fidelity when round-tripping elevation, reduce file size, and reduce
+silliness in files caused by repeating decimals in insignificant
digits.
</para>
<para>
Precisions beyond this are not currently obtainable.
</para>
<para>
-This value is ignored on read and has no impact on the internal
+This value is ignored on read and has no impact on the internal
representation of data.
</para>
Write Garmin-specific extensions, when such data is available, to the GPX.
Notably, depth, temperature, proximity, display color, ambient temperature,
heart rate, and cadence are read when they are available in the source data.
- This data can, of course, only be read by GPX readers that know about the
+ This data can, of course, only be read by GPX readers that know about the
Garmin gpxtpx and gpxx extended namespaces.
</para>
<para>
<para>
-This option specifies the version of the GPX specification to use for
+This option specifies the version of the GPX specification to use for
output. The default version is 1.0 unless one or more of the input files
is GPX 1.1, then it's 1.1. The only other valid value for this
option is 1.1.
</para>
<para>
Notice that this is not a full scale XML schema conversion. In particular,
-if you have a GPX 1.0 file that has extended namespaces in it (such as a
+if you have a GPX 1.0 file that has extended namespaces in it (such as a
pocket query from Geocaching.com) just writing it with this option will
result in a horribly mangled GPX file as we can't convert the schema data.
</para>
<para>
-Use this option to encrypt hints from Groundspeak GPX files.
+Use this option to encrypt hints from Groundspeak GPX files.
</para>
<para>
-Use this option to include Groundspeak cache logs in the created document.
+Use this option to include Groundspeak cache logs in the created document.
</para>
<para>
-Because the format supports only one track, this option may be used
-on output to select a single track from a collection of
-tracks read from a more expressive format. If you have, say, a
+Because the format supports only one track, this option may be used
+on output to select a single track from a collection of
+tracks read from a more expressive format. If you have, say, a
<link linkend="fmt_gpx">gpx</link> file that contains two tracks, you may
use this option to write them one at a time to individual files.
</para>
<para>
This option isn't entirely clear. It appears to be a unique number
for each track that is used for coloring on the main display. So if you
- want two tracks to have different colors, set the track numbers to
+ want two tracks to have different colors, set the track numbers to
different values.
</para>
<para>
-<para>Specifies a backup file for the binary logger data. New waypoints from the logger will be appended to an existing
+<para>Specifies a backup file for the binary logger data. New waypoints from the logger will be appended to an existing
backup file. This allows you to create "endless" binary logger files which, for example, could contain the waypoint data of a whole year.</para>
<para>The backup file can be read with gpsbabel by using the itracku format.</para>
-<para>Will only pass waypoints along to filters and output formats that are not new, i.e. that are not already stored in the
+<para>Will only pass waypoints along to filters and output formats that are not new, i.e. that are not already stored in the
backup file. This option can only be used with the backup option.</para>
-<para>Using this option allows you to output the waypoints of your latest trip with gpsbabel while keeping an endless log of all waypoints
+<para>Using this option allows you to output the waypoints of your latest trip with gpsbabel while keeping an endless log of all waypoints
in the backup file.</para>
<example id="itracku-new">
- <title>Download from the data logger and append the new logger data to a backup file. Output only the new
+ <title>Download from the data logger and append the new logger data to a backup file. Output only the new
waypoints.</title>
<para><userinput>gpsbabel -i itracku,auto,backup=itracku.bak,new -f dummy -o gpx -F out.gpx</userinput></para>
</example>
<para>
-This option specifies the line color as a hexadecimal number in
+This option specifies the line color as a hexadecimal number in
AABBGGRR format, where A is alpha, B is blue, G is green, and R is red.
</para>
<para>
When this option is nonzero, GPSBabel draws lines between points in
tracks and routes. The default value for this option is 1, which causes
-lines to be drawn by default. To disable line-drawing, specify
+lines to be drawn by default. To disable line-drawing, specify
<option>lines=0</option>.
</para>
writing coordinate values.
Precision is the number of digits after the decimal point. The default
precision is 6. We limit the number of places we write to improve the
-fidelity when round-tripping thata, reduce file size, and reduce
-silliness in files caused by repeating decimals in insignificant
+fidelity when round-tripping thata, reduce file size, and reduce
+silliness in files caused by repeating decimals in insignificant
digits.
</para>
<para>
-As a guideline, at the equator, five decimal places is about 1.1 m,
+As a guideline, at the equator, five decimal places is about 1.1 m,
placing it below the accuracy of commodity consumer GPS gear. Six places
is 0.11 m, achievable via surveyor grade and differential corrected GPS.
Seven is 11 millimeters.
</para>
<para>
-This value is ignored on read and has no impact on the internal
+This value is ignored on read and has no impact on the internal
representation of data.
</para>
If this option is used without a value then the colors are automatically selected such
that the spectrum will be rotated through once for all the tracks and once for all the routes.
If this option is used with a positive value then the value is interpreted as the number of degrees
-in the color circle between adjacent tracks or routes.
+in the color circle between adjacent tracks or routes.
This option takes precedence over line_color.
</para>
<para>
- If set, this options creates directional icons for trackpoints. Arrows
+ If set, this options creates directional icons for trackpoints. Arrows
will show the direction of travel on drawn tracks and routes.
</para>
<para>
-Units is a simple option. Specify 's' for "statute" (miles, feet, and
+Units is a simple option. Specify 's' for "statute" (miles, feet, and
other things that don't sensibly convert to each other, but are craved
by Americans), 'm' for "metric", 'n' for "nautical" or 'a' for "aviation". Default is 's'.
</para>
it is currently only able to generate USR format 2, 3, or 4 due to the lack of
detailed information on some of the data contained in the other formats.
</para>
-
+
<para>
By default, GPSBabel will generate USR version 2 data if the output format is
specified as <emphasis>lowranceusr</emphasis>.
USR file format that adds waypoint depth. Lowrance recommends that this USR version
be used when transferring user data to systems such as
LMS, LCX, and so on. Specify "3" to output USR version 3 data
- on write.
+ on write.
</para>
<para>
Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments. It
-is therefore sometimes convenient to limit the number of waypoint
+is therefore sometimes convenient to limit the number of waypoint
comments written to the receiver. For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
<para>
This option causes GPSBabel to use the given baud rate for serial
- communications. It must match the given baud rate on the receiver. The
+ communications. It must match the given baud rate on the receiver. The
default value matches the default on the receiver, 4800.
</para>
<para>
Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments. It
-is therefore sometimes convenient to limit the number of waypoint
+is therefore sometimes convenient to limit the number of waypoint
comments written to the receiver. For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
<para>
Certain firmware versions have problems handling this which makes transfers
unnecessarily slow. Transfers on all units at high serial speeds are also
-severely restricted by this process.
+severely restricted by this process.
</para>
<para>
In controlled environments (good cables, low electrical noise, receiving
from the unit, not doing donuts with the unit set to "track up" at a 150
-mile scale with 500 waypoints on the screen) it is sometimes useful to
+mile scale with 500 waypoints on the screen) it is sometimes useful to
release that safety belt by using the "noack" suboption.
</para>
<para>
This is a convenient option to use in automated processes where you want
to ensure the units starts with a clean state before sending waypoints to
-it. Using this option on transmit is a better idea than doing it on
+it. Using this option on transmit is a better idea than doing it on
receive since the latter would erase all the waypoints before asking the
unit to send all the waypoints.
</para>
Magellan receivers allow a maximum of 200 waypoint comments. Unfortunately,
DirectRoute uses waypoint comments to provide next turn directions for
navigation pop-ups and that comes from that pool of 200 comments. It
-is therefore sometimes convenient to limit the number of waypoint
+is therefore sometimes convenient to limit the number of waypoint
comments written to the receiver. For example, a geocacher might want
to upload 400 waypoints, but only 190 with comments so that DirectRoute
could provide driving directions for the next ten turns.
<para>
- The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
- You can program the location of each either by a keypress on the device (which uses the actual position)
+ The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
+ You can program the location of each either by a keypress on the device (which uses the actual position)
or with GPSBabel (which lets you use any position)
- You can set the location of "Bar" with the 'Bar' option. Use ':' as the delimiter between latitude, longitude and altitude.
+ You can set the location of "Bar" with the 'Bar' option. Use ':' as the delimiter between latitude, longitude and altitude.
You can leave altitude out, in which case it is assumed to be zero.
Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</para>
</para>
<para>
Sets the Bar symbols' latitude to 38.99809N longitude to 86.34662W and altitude to 0m.
- If you select the Bar symbol on miniHomer, the display will show the direction and distance to
+ If you select the Bar symbol on miniHomer, the display will show the direction and distance to
this location as soon as it has a satellite fix.
</para>
</example>
<para>
- The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
- You can program the location of each either by a keypress on the device (which uses the actual position)
+ The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
+ You can program the location of each either by a keypress on the device (which uses the actual position)
or with GPSBabel (which lets you use any position)
- You can set the location of "Boat" with the 'Boat' option. Use ':' as the delimiter between latitude, longitude and altitude.
+ You can set the location of "Boat" with the 'Boat' option. Use ':' as the delimiter between latitude, longitude and altitude.
You can leave altitude out, in which case it is assumed to be zero.
Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</para>
</para>
<para>
Sets the Boat symbols' latitude to 32.29287N longitude to 64.77527E and altitude to 0m.
- If you select the Home symbol on miniHomer, the display will show the direction and distance to
+ If you select the Home symbol on miniHomer, the display will show the direction and distance to
this location as soon as it has a satellite fix.
</para>
</example>
<para>
- The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
- You can program the location of each either by a keypress on the device (which uses the actual position)
+ The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
+ You can program the location of each either by a keypress on the device (which uses the actual position)
or with GPSBabel (which lets you use any position)
- You can set the location of "Car" with the 'Car' option. Use ':' as the delimiter between latitude, longitude and altitude.
+ You can set the location of "Car" with the 'Car' option. Use ':' as the delimiter between latitude, longitude and altitude.
You can leave altitude out, in which case it is assumed to be zero.
Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</para>
</para>
<para>
Sets the Car symbols' latitude to 25.272309S longitude to 153.235330E and altitude to 0m.
- If you select the Car symbol on miniHomer, the display will show the direction and distance to
+ If you select the Car symbol on miniHomer, the display will show the direction and distance to
this location as soon as it has a satellite fix.
</para>
</example>
<para>
- The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
- You can program the location of each either by a keypress on the device (which uses the actual position)
+ The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
+ You can program the location of each either by a keypress on the device (which uses the actual position)
or with GPSBabel (which lets you use any position)
- You can set the location of "Heart" with the 'Heart' option. Use ':' as the delimiter between latitude, longitude and altitude.
+ You can set the location of "Heart" with the 'Heart' option. Use ':' as the delimiter between latitude, longitude and altitude.
You can leave altitude out, in which case it is assumed to be zero.
Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</para>
</para>
<para>
Sets the Heart symbols' latitude to 36.1269N longitude to 115.1698W and altitude to 0m.
- If you select the Heart symbol on miniHomer, the display will show the direction and distance to
+ If you select the Heart symbol on miniHomer, the display will show the direction and distance to
this location as soon as it has a satellite fix.
</para>
</example>
<para>
- The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
- You can program the location of each either by a keypress on the device (which uses the actual position)
+ The device provides a location finder display supporting five locations "Home", "Car", "Boat", "Heart", "Bar".
+ You can program the location of each either by a keypress on the device (which uses the actual position)
or with GPSBabel (which lets you use any position)
- You can set the location of "Home" with the 'Home' option. Use ':' as the delimiter between latitude, longitude and altitude.
+ You can set the location of "Home" with the 'Home' option. Use ':' as the delimiter between latitude, longitude and altitude.
You can leave altitude out, in which case it is assumed to be zero.
Note that GPSBabel terminates after writing the location info to the device, i.e. no logging data will be read from it.
</para>
</para>
<para>
Sets the Home symbols' latitude to 3.066667S longitude to 37.359167E and altitude to 5895m.
- If you select the Home symbol on miniHomer, the display will show the direction and distance to
+ If you select the Home symbol on miniHomer, the display will show the direction and distance to
this location as soon as it has a satellite fix.
</para>
</example>
<para>
-This function is identical to the init-baud file function of skytraq module.
+This function is identical to the init-baud file function of skytraq module.
</para>
<para>The "initbaud" option might be helpful if autodetection fails or takes too long. With this option you
can tell GPSBabel the baud rate the device is currently set to. In contrast, the option "baud" specifies
encountered.
We observed that sometimes the device doesn't report the correct number of used sectors, which confuses the Windows
software, so that it might not get all trackpoints.
-In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you).</para>
+In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you).</para>
<para>
-Two major strains of Mobile Mapper files have been identified in the wild. Version 17 is reported as "Memory Map OS Edition 2004, Versio 4.2.3 Build 432" and version 18 is used by the large majority of current files. We can read either and when writing, we write version 18 by default.
+Two major strains of Mobile Mapper files have been identified in the wild. Version 17 is reported as "Memory Map OS Edition 2004, Versio 4.2.3 Build 432" and version 18 is used by the large majority of current files. We can read either and when writing, we write version 18 by default.
</para>
<para>
-If you have a particularly old Mobile Mapper installation, it may complain "This file was created with a newer version of the Software" when reading our output.You can get around this if force GPSBabel to create the old format with this option.
+If you have a particularly old Mobile Mapper installation, it may complain "This file was created with a newer version of the Software" when reading our output.You can get around this if force GPSBabel to create the old format with this option.
</para>
<example id="mmo_ver">
<title>Forcing creation of old Mobile Mapper files</title>
-<para>This option processes a set of Locus fixes, by downloading it from an
+<para>This option processes a set of Locus fixes, by downloading it from an
attached USB device or by reading records stored in a normal file.</para>
-<para>You might want to disable this option if all you want to do is erase the memory
+<para>You might want to disable this option if all you want to do is erase the memory
or display the device status. Downloading a large dataset can take several minutes
and while that is happening no other device commands can be executed.</para>
<para>
-This option specifies the name of the icon to use for
+This option specifies the name of the icon to use for
non-stealth, encrypted access points.
</para>
<para>
-This option specifies the name of the icon to use for
+This option specifies the name of the icon to use for
non-stealth, non-encrypted access points.
</para>
<para>
-This option specifies the name of the icon to use for
+This option specifies the name of the icon to use for
stealth, encrypted access points.
</para>
<para>
-This option specifies the name of the icon to use for
+This option specifies the name of the icon to use for
stealth, non-encrypted access points.
</para>
<para>
- When writing NMEA realtime positioning data, append to the
+ When writing NMEA realtime positioning data, append to the
output file instead of truncating it on each successive position
fix.
</para>
<para>
-On input, track points with times but no dates will have this date applied.
+On input, track points with times but no dates will have this date applied.
</para>
<para>
This is necessary because some NMEA sentences contain times but no dates. If
-this option is not specified and the date cannot be determined from one or
+this option is not specified and the date cannot be determined from one or
more of the available NMEA sentences, the tracks will be discarded.
</para>
<para>
- This option writes the Gisteq format - which has the extension of .GPS -
- to allow third-party GPS hardware with the Gisteq PhotoTrackr software.
+ This option writes the Gisteq format - which has the extension of .GPS -
+ to allow third-party GPS hardware with the Gisteq PhotoTrackr software.
</para>
<para>
The Gisteq PhotoTrackr is a GPS data logger hardware and software package
digital photos with the timestamps in the tracking data. In doing so, the
software plots the locations of the photos using Google Maps. The logging
format used by the Gisteq hardware is very close to NMEA format, but with a
- few small quirks.
+ few small quirks.
</para>
<para>
-More information can be found at the
+More information can be found at the
<ulink url="http://www.gisteq.com/">Gisteq</ulink> site.
</para>
<para>
-This option tells GPSBabel whether to read (on input) or write (on output)
-GPGGA sentences. The default is to read or write GPGGA sentences. To
+This option tells GPSBabel whether to read (on input) or write (on output)
+GPGGA sentences. The default is to read or write GPGGA sentences. To
disable GPGGA sentences, specify <option>gpgga=0</option>.
</para>
<para>
<para>
-This option tells GPSBabel whether to read (on input) or write (on output)
-GPGSA sentences. The default is to read or write GPGSA sentences. To
+This option tells GPSBabel whether to read (on input) or write (on output)
+GPGSA sentences. The default is to read or write GPGSA sentences. To
disable GPGSA sentences, specify <option>gpgsa=0</option>.
</para>
<para>
GPGSA sentences contain information on the quality of the positional fix
and the individual satellites from which it was derived. However, GPSBabel
-neither reads nor writes the individual satellite data. On input, the
+neither reads nor writes the individual satellite data. On input, the
satellite fields are ignored and on output they are left blank.
</para>
<para>
-This option tells GPSBabel whether to read (on input) or write (on output)
-GPRMC sentences. The default is to read or write GPRMC sentences. To
+This option tells GPSBabel whether to read (on input) or write (on output)
+GPRMC sentences. The default is to read or write GPRMC sentences. To
disable GPRMC sentences, specify <option>gprmc=0</option>.
</para>
<para>
-GPRMC sentences contain the "recommended minimum" positional information,
-including date and time, heading, and velocity. Note that they do not
+GPRMC sentences contain the "recommended minimum" positional information,
+including date and time, heading, and velocity. Note that they do not
include altitude. For altitude, you will have to include GPGGA sentences.
</para>
<para>
-This option tells GPSBabel whether to read (on input) or write (on output)
-GPVTG sentences. The default is to read or write GPVTG sentences. To
+This option tells GPSBabel whether to read (on input) or write (on output)
+GPVTG sentences. The default is to read or write GPVTG sentences. To
disable GPVTG sentences, specify <option>gpvtg=0</option>.
</para>
<para>
GPVTG sentences contain information about the heading and the speed at the
-time of the fix. They do not contain any location information; for that
+time of the fix. They do not contain any location information; for that
you will need either or both of GPGGA or GPRMC.
</para>
<para>
This option tells GPSBabel to pause between individual track records when
-used on output. This may be used with appropriate external software or
+used on output. This may be used with appropriate external software or
hardware to simulate a GPS receiver for testing purposes. On Unix, for
example, you may use a named pipe to feed the output from GPSBabel to gpsd.
</para>
pause between trackpoints.)
</para>
<para>
-If this option is specified with a negative value, the time between adjacent
+If this option is specified with a negative value, the time between adjacent
trackpoints will be computed and used for the length of the pause. That is,
-if your trackpoints are 5 seconds apart, GPSBabel will pause 5 seconds
+if your trackpoints are 5 seconds apart, GPSBabel will pause 5 seconds
between trackpoints.
</para>
<para>
-Note that very long tracks may be subject to clock drift, as GPSBabel does
-not take into account the amount of time it may take to write the NMEA
+Note that very long tracks may be subject to clock drift, as GPSBabel does
+not take into account the amount of time it may take to write the NMEA
sentences. Also, there is no guarantee that it will pause for exactly the
-specified number of seconds between samples; different operating systems
+specified number of seconds between samples; different operating systems
will allow greater or lesser precision for timers, so actual precision may
be as much as plus or minus 100 milliseconds.
</para>
<para>
-If you are using this option with compressed or simplified tracks from
-your handheld GPS receiver, you might find the
+If you are using this option with compressed or simplified tracks from
+your handheld GPS receiver, you might find the
<link linkend="filter_interpolate">interpolate</link> filter useful.
</para>
<para>
-This option specifies the maximum length to be used for waypoint names in
-the GPWPL sentence. Longer names will be shortened to no more than this
+This option specifies the maximum length to be used for waypoint names in
+the GPWPL sentence. Longer names will be shortened to no more than this
length, but all waypoint names will remain unique.
</para>
<para> Use this value as custom created_by value in an OSM file.</para>
<para>
-With this option, the given string is added as the 'created_by' field in
+With this option, the given string is added as the 'created_by' field in
all the created nodes and ways.
</para>
<para>
- In normal case GPSBabel creates for each track a separate file (track.plt, track-1.plt, ...).
+ In normal case GPSBabel creates for each track a separate file (track.plt, track-1.plt, ...).
With this option all tracks will be written into one file. A '1' in the third field of the
trackpoint record signals the beginning of a new track.
</para>
<para>
- This option, specified in meters, allows you to set the proximity of
+ This option, specified in meters, allows you to set the proximity of
written waypoints.
</para>
This is particularly useful when used in combination with the 'sort'
filter.
</para>
-
+
<para>
This option specifies the internal name for the document. This is the name
that appears in your document reader, not the name of the file that is created
-on your computer.
+on your computer.
</para>
<para>
-Use this option to encrypt hints from Groundspeak GPX files.
+Use this option to encrypt hints from Groundspeak GPX files.
</para>
<para>
-Use this option to include Groundspeak cache logs in the created document.
+Use this option to include Groundspeak cache logs in the created document.
</para>
<para>
-To suppress the dashed lines between waypoints, use this option.
+To suppress the dashed lines between waypoints, use this option.
</para>
<para>
-This option specifies the input and output format for the date. The format
+This option specifies the input and output format for the date. The format
is written similarly to those in Windows. An example format is "YYMMDD".
</para>
Note that if your goal is to create an arc or other CSV file, you
should use 'none' (or not use this option, which is the same
thing.)</para>
-
+
routes for each street, creating a new route at each turn point. For
obvious reasons, 'split' cannot be used at the same time as the
'turns_only' or 'turns_important' options.</para>
-
+
it were a track, synthesizing times starting from the current time, using
the estimated travel times specified in your route file (you can change your
travel speeds in the DeLorme product you used to create the route file.)</para>
-
+
simplification process will remove the points corresponding to turns
only after it has removed all other route points.
</para>
-
+
<para> This option causes GPSBabel to read only the
waypoints associated with named turns. This should create a list of
waypoints that correspond to the itinerary from Street Atlas.</para>
-
+
<para>
gps-utc-offset is used to override the built-in table of offsets of
-the offset between GPS time and UTC time. This chipset reports only
+the offset between GPS time and UTC time. This chipset reports only
GPS time to the host and relies on software to know every time an adjustment
is made. Since GPS time offsets can change without a new version of GPSBabel
is released, those that care about total accuracy can override it.
<thead>
<row>
<entry>Starting from:</entry>
- <entry>gps-week-rollover value:</entry>
+ <entry>gps-week-rollover value:</entry>
</row>
</thead>
<tbody>
encountered.
We observed that sometimes the device doesn't report the correct number of used sectors, which confuses the Windows
software, so that it might not get all trackpoints.
-In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you).</para>
+In contrast, our algorithm ensures that everything is being read (please report if it doesn't work for you).</para>
0 -o unicsv -F -</userinput>
</para>
<para>
- Sets latitude and longitude of the location finder to N12.34 and
- W56.78 respectively.
- The arrows on the device will point you to this location as soon as
+ Sets latitude and longitude of the location finder to N12.34 and
+ W56.78 respectively.
+ The arrows on the device will point you to this location as soon as
it has a satellite fix.
</para>
</example>
<para>
- The date part of the GPS timestamp which corresponds to a known position
+ The date part of the GPS timestamp which corresponds to a known position
in the video.
</para>
<para>
- Format is yyyymmdd. This option must be used together with
- <option>gps_time</option>; if one or both are missing, the timestamp of the
+ Format is yyyymmdd. This option must be used together with
+ <option>gps_time</option>; if one or both are missing, the timestamp of the
first GPS trackpoint is used.
</para>
<para>
- The video position to which the timestamp corresponds can be set with the
+ The video position to which the timestamp corresponds can be set with the
<option>video_time</option> option.
</para>
<para>
- The time part of the GPS timestamp which corresponds to a known position
+ The time part of the GPS timestamp which corresponds to a known position
in the video.
</para>
<para>
- Format is hhmmss. This option must be used together with
+ Format is hhmmss. This option must be used together with
<option>gps_date</option>; if one or both are missing, the timestamp of the
first GPS trackpoint is used.
</para>
<para>
- The video position to which the timestamp corresponds can be set with the
+ The video position to which the timestamp corresponds can be set with the
<option>video_time</option> option.
</para>
Format is hhmmss. If omitted, 0:00:00 (beginning of video) is assumed.
</para>
<para>
- The GPS timestamp can be set with the <option>gps_time</option> and
+ The GPS timestamp can be set with the <option>gps_time</option> and
<option>gps_date</option> options.
</para>
<para>
-Use this option to encrypt hints from Groundspeak GPX files.
+Use this option to encrypt hints from Groundspeak GPX files.
</para>
<para>
-Use this option to include Groundspeak cache logs in the created document.
+Use this option to include Groundspeak cache logs in the created document.
</para>
<para>
-To suppress the dashed lines between waypoints, use this option.
+To suppress the dashed lines between waypoints, use this option.
</para>
<example id="text_splitoutput">
<title>Example for splitoutput option to text format</title>
<para>
- If "MyPQ.gpx" contains five waypoints,
+ If "MyPQ.gpx" contains five waypoints,
<userinput>
gpsbabel -i gpx -f MyPocketQuery -o text,split -F blah
</userinput>
<para>The option 'datum="datum name"' can be used to override
the default of NAD27 ("N. America 1927 mean") which is correct for the
continental U.S.</para> <para>Any legal <link linkend="Datums">datum supported
-by GPSBabel</link> may be used. For example, points in Hawaii should
+by GPSBabel</link> may be used. For example, points in Hawaii should
use "Old Hawaiian_mean".</para>
-
+
-<para>\r
-This option lets you configure how many digits GPSBabel uses for numbering generated route point names.\r
-</para>\r
-<para>\r
-When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices.\r
-</para>\r
-<para>\r
-Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option.\r
-</para>\r
-<example id="transform_rptdigits">\r
-<title>Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers.</title>\r
-<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx</userinput></para>\r
-</example>\r
+<para>
+This option lets you configure how many digits GPSBabel uses for numbering generated route point names.
+</para>
+<para>
+When GPSBabel creates route points during the transformation process these points are sequentially numbered and named "RPTnnn" where nnn represent the number. By default GPSBabel uses 3 digits for these numbers. Rationale: This way a large number of route points can be uniquely named while the generated names are limited to 6 characters. This limitation is imposed by specific GPS devices.
+</para>
+<para>
+Using this option GPSBabel can be configured to use less or more digits for the generated names. This option is best used in conjunction with the rptname option.
+</para>
+<example id="transform_rptdigits">
+<title>Convert a GPX track to a GPX route, deleting the original track, using 2 digits for the generated numbers.</title>
+<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptdigits=2 -o gpx -F route.gpx</userinput></para>
+</example>
-<para>\r
-With this option you can decide to let GPSBabel name generated route points according to their source track name.\r
-</para>\r
-<para>\r
-GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>\r
-<para>\r
-Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes.\r
-</para>\r
-<example id="transform_rptname">\r
-<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>\r
-<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx</userinput></para>\r
-</example>\r
+<para>
+With this option you can decide to let GPSBabel name generated route points according to their source track name.
+</para>
+<para>
+GPSBabel creates route points during the transformation process named "RPTnnn" where nnn is a numeric part.</para>
+<para>
+Using this option GPSBabel can be configured to replace the "RPT" part of the generated names by the name of the source track during the transformation process. This is especially useful if several differently named tracks are contained in the source file which should each be transformed into routes.
+</para>
+<example id="transform_rptname">
+<title>Convert a GPX track to a GPX route, deleting the original track, naming the generated points like the original track name.</title>
+<para><userinput>gpsbabel -i gpx -f track.gpx -x transform,wpt=trk,del,rptname=y -o gpx -F route.gpx</userinput></para>
+</example>
<para>
- This option specifies the datum to be used on output. Valid values for this
+ This option specifies the datum to be used on output. Valid values for this
option are listed in <xref linkend="Datums" />.
</para>
file describing the file. Field names are separated by a '+' character.
The list of field names is exactly that allowed in the first line of a
unicsv file without this option.
-</para>
+</para>
<example id="unicsv_fields">
<title>Example for unicsv fields option to describe input file.</title>
<userinput>
gpsbabel -i unicsv,fields=lat+lon+description -f file.csv -o gpx -F file.gpx
</userinput>
- declares that file.csv has three fields, latitude, longitude,
+ declares that file.csv has three fields, latitude, longitude,
and description, in that order.
</para>
<para>
This option specifies the local time zone to use when writing times. It
-is specified as an offset from Universal Coordinated Time (UTC) in hours.
+is specified as an offset from Universal Coordinated Time (UTC) in hours.
Valid values are from -23 to +23.
-</para>
+</para>
<para>
-This option specifies the GPS datum to be used on read or write. Valid values for this
+This option specifies the GPS datum to be used on read or write. Valid values for this
option are listed in <xref linkend="Datums" />.
</para>
built-in xcsv-based styles; they have prebuilt style definitions.
</para>
<para>
-For information on the format of xcsv style files, see
+For information on the format of xcsv style files, see
<xref linkend="Styles" />.
</para>
<para>
-This option specifies the base name to prepend to a URL on output. This
+This option specifies the base name to prepend to a URL on output. This
might be useful if an input file contains URLs in a relative format and you
need them to be in an absolute format.
</para>
<para>This is the format for the Ricoh 500SE GPS logging camera.
</para>
<para>
- This camera creates log files on the SD card in a folder name "GPSLOG" that
- are named "YYMMDDNN.LOG" where NN increments from 00 through 99. The camera
- appends new tracks into the current file, hence the "new track" field. When
- the current file reaches about 500K, NN increments and logging continues into
- the next file. Therefore, there may be multiple tracks in each log
- file, and tracks may span one or more files.
+ This camera creates log files on the SD card in a folder name "GPSLOG" that
+ are named "YYMMDDNN.LOG" where NN increments from 00 through 99. The camera
+ appends new tracks into the current file, hence the "new track" field. When
+ the current file reaches about 500K, NN increments and logging continues into
+ the next file. Therefore, there may be multiple tracks in each log
+ file, and tracks may span one or more files.
</para>
<para>
GPSBabel will recognize the "new track" field and will generate a new track,
so if you specify multiple files in the correct order, your tracks will be
- automatically split sensibly.
+ automatically split sensibly.
</para>
<para>
For additional tips, see the
<ulink url="/formats/s_and_t/Importing_into_Microsoft_Streets_and_Trips_2003.html">gpsbabel.org</ulink>
</para>
<para>
- We have an additional page describing how to solve the
- <ulink url="/formats/s_and_t/TripPlanning.html">traveling salesman problem with
- Streets & Trips</ulink> to efficiently optimize a trip with many stops, such as
+ We have an additional page describing how to solve the
+ <ulink url="/formats/s_and_t/TripPlanning.html">traveling salesman problem with
+ Streets & Trips</ulink> to efficiently optimize a trip with many stops, such as
is often made by geocachers.
</para>
<!--
<para>
- This format has nothing to do with the <link linkend="fmt_msroute1"> .est/axe format</link>
+ This format has nothing to do with the <link linkend="fmt_msroute1"> .est/axe format</link>
used by this program to store routes.
</para>
-->
Since modern versions of Streets and Trips support reading GPX, this format is probably
not so useful.
</para>
-
+
-
-
+
+
<para> This format is for DeLorme Street Atlas USA 2004 Plus and later.
</para>
<para> For geocachers importing data from a tool like GSAK or
second to last column, change URL to none and then click next. Use the
same name you used the first time but add -Flag to it.
</para>
-
+
-<para>
+<para>
This format reads route files from many DeLorme mapping products.
It supports the anr, rte, and rtd formats as either tracks or
routes.</para>
versions of DeLorme software; older versions didn't store the turn
information with the route.
</para>
-
+
<tgroup cols="4">
<thead>
<row>
- <entry>Manufacturer</entry>
- <entry>Model</entry>
- <entry>USB (baud)</entry>
+ <entry>Manufacturer</entry>
+ <entry>Model</entry>
+ <entry>USB (baud)</entry>
<entry>Bluetooth (baud)</entry>
</row>
</thead>
<para>
- With this format we support Sportsim trackfiles located in zipped .ssz archives.
+ With this format we support Sportsim trackfiles located in zipped .ssz archives.
</para>
<para>
- Currently we cannot read zipped files directly with GPSBabel. So you have
+ Currently we cannot read zipped files directly with GPSBabel. So you have
to extract the archive before you can use any file. The trackfiles have .txt extensions.
</para>
<para>
<ulink url="http://www.sportsim.com/web/index.php?url=about">From the Sportsim homepage:</ulink>
</para>
<para>
- Sportsim provide software applications and web-based graphically
+ Sportsim provide software applications and web-based graphically
simulated performance information and image solutions to outdoor active people.
</para>
will need to synchronize both. For this purpose, film the display of
your GPS receiver (or any other device) showing GPS time. (Important:
you need precise GPS time for this; local time, especially from an
- inaccurate clock, will not do for this.)
+ inaccurate clock, will not do for this.)
</para>
<para>
Determine the position in the video at which the GPS time is visible
<para>
This format, like the <link linkend="fmt_custom">custom</link> format, is
mainly used for the purpose of testing GPSBabel. It is supposed to contain
-one field for each piece of information supported by the
+one field for each piece of information supported by the
<link linkend="fmt_xcsv">xcsv</link> format writer, but it may not be entirely
in sync with the documentation at <xref linkend="Styles" />.
</para>
<para>
-TEF, internally called "TourExchangeFormat", is an XML based export format
+TEF, internally called "TourExchangeFormat", is an XML based export format
used by Map&Guide <productname>Motorrad-Routenplaner 2005/06</productname>.
</para>
<para>
this format.
</para>
<para>
-GPSBabel also supports the <link linkend="fmt_bcr">bcr</link> format, which
+GPSBabel also supports the <link linkend="fmt_bcr">bcr</link> format, which
may also be used with this program and supports both reading and writing.
</para>
<para><userinput> gpsbabel -r -i tef,routevia -f in.xml -o gpx -F out.gpx</userinput></para>
-
+
Groundspeak extensions and writes a text file with encrypted hints:
</para>
<para><userinput>gpsbabel -i gpx -f 12345.gpx -o text,encrypt -F 12345.txt</userinput></para>
-
+
-
-
+
+
<para> This format can read and write <ulink url="http://www.tomtom.com">TomTom</ulink> .ov2 (POI) files,
as used by the TomTom GO and TomTom Navigator. It has been tested
with an original TomTom GO running version 5.00 of the TomTom
.bmp file for the icon. It should be 22x22 and 16 colors, and have
the same name (not including the extension) as the .ov2 file.
</para>
-
+
-
-
+
+
<para>National Geographic Topo! Waypoint and Route Format. This module
reads and writes .TPG files created by various editions of NG Topo!
Reading/writing of route data is not supported yet.</para>
<para>Contributed by Alex Mottram.</para>
-
+
-
-
+
+
<para>This module reads .TPO files created by various editions
of NG Topo!. For version 2.x files it will only read tracks. For
version 3.x files it will read Tracks/Routes/Waypoints/Map
<para>2.x support contributed by Steve Chamberlin. 3.x support
contributed by Curt Mills.</para>
-
+
<para>
- This module reads tracks from .TPO files created by
+ This module reads tracks from .TPO files created by
National Geographic Topo! version 2.x
</para>
<para>
- Contributed by Steve Chamberlin.
+ Contributed by Steve Chamberlin.
</para>
-
+
-
-
+
+
<para>The vCard output is intended to be in a format that
enables waypoints to be viewed with an Apple iPod. This is achieved by
mapping waypoint fields into vCard fields that can be displayed as
iPod manual for instructions), the resulting VCF file should be moved
into the iPod 'Contacts' folder. As an alternative, Mac OS X users may
prefer to drag the VCF file into their address book and synchronize
-with the iPod using iSync.
+with the iPod using iSync.
</para>
-
+
-<para>Serial download protocol for the
+<para>Serial download protocol for the
<productname>Wintec WBT-200</productname> and
-<productname>Wintec WBT-201</productname>
-<productname>Wintec WBT-1000</productname>
+<productname>Wintec WBT-201</productname>
+<productname>Wintec WBT-1000</productname>
GPS data loggers. Although untested it is expected that this will also support the WBT-100.</para>
<para>
<ulink url="http://www.semsons.com/wiwbmu3gpsre2.html">Wintec WBT-201</ulink>
<para>
Internally, this is actually a serial device that has a serial/USB adapter
built into it. It uses the CP210x chip by Silicon labs. You will probably
-need a driver for this chip. The product ships with one for Windows.
-The Linux 210x driver seems to work fine. Mac users will need to download
+need a driver for this chip. The product ships with one for Windows.
+The Linux 210x driver seems to work fine. Mac users will need to download
the <ulink url="http://www.silabs.com/tgwWebApp/public/web_content/products/Microcontrollers/USB/en/mcu_vcp.htm">Mac driver for CP210x</ulink>.
</para>
<para>
GPSBabel does not try to offer an interface to configure these units. That
-is left to the Windows software that comes with it or tools like the
+is left to the Windows software that comes with it or tools like the
<ulink url="http://www.daria.co.uk/gps">WBT 201 Viewer</ulink> for Mac OS/X
and Linux.
</para>
-<para>This format supports Wintec .tec files, such as appear on the
+<para>This format supports Wintec .tec files, such as appear on the
<productname>Wintec WBT-202</productname> data logger.
</para>
<para>
The WinTec WBT-202 stores tracks and waypoints on an internal
MICRO-SD Memory card. The log files can be accessed by connecting to an USB
host and setting the device into a mass storage device (MSD) mode. To enter
-this mode, attach it to the computer, then hold the power button until the
+this mode, attach it to the computer, then hold the power button until the
GPS and Bluetooth LEDs go out. It will then behave like an USB Memory stick.
and individual files containing your tracks will show up on the "disk" with
names ending in .tes. You can use GPSBabel to read these files directly
to the .TK2 files created by Wintec's Time Machine software for Windows.
</para>
<para>
-Despite the physical similarity to the
+Despite the physical similarity to the
<productname>Wintec WBT-201</productname>, this is believed to be a rather
-different product. While this GPS probably works fine for
-<link linkend="tracking">realtime tracking</link> over the bluetooth or
+different product. While this GPS probably works fine for
+<link linkend="tracking">realtime tracking</link> over the bluetooth or
serial lines (once you have appropriate serial drivers), it's expected
-to not work with GPSBabel's <link linkend="fmt_wbt">GPSBabel WBT
+to not work with GPSBabel's <link linkend="fmt_wbt">GPSBabel WBT
Protocol</link> module.
</para>
<para>
-This format is a very flexible module that can be used to read or write
-nearly any plain-text record-based waypoint file. This flexibility is
-achieved by combining this format with "style" files that describe the
+This format is a very flexible module that can be used to read or write
+nearly any plain-text record-based waypoint file. This flexibility is
+achieved by combining this format with "style" files that describe the
format of the waypoint files.
</para>
<para>
-There are several formats built in to GPSBabel that use the underlying xcsv
+There are several formats built in to GPSBabel that use the underlying xcsv
machinery. Each of those formats takes the same options as the xcsv format,
-with the obvious exception of the <option>style</option> option.
-Those formats are all based on style files that can be found in
+with the obvious exception of the <option>style</option> option.
+Those formats are all based on style files that can be found in
the "style" directory in the GPSBabel source distribution.
</para>
projects / gpsbabel.git / commitdiff